Skip to content

usage of proxies is broken in nightly release (net::ERR_FAILED) #2698

@richie256

Description

@richie256

Expected Behavior

Using proxies with the docker nightly build or nodejs (using the latest code from github) should works fine without net::ERR_FAILED error.

Current Behavior

Using proxies with the nightly build or nodejs (using the latest code from github) return net::ERR_FAILED error. It works as expected using latest docker image.

Steps to Reproduce

  1. Configure the dotenv and global.proxies file with valid proxies
  2. Launch docker run -it --rm --env-file ./dotenv -v $(pwd)/global.proxies:/app/global.proxies ghcr.io/jef/streetmerchant:nightly

OR

  1. Clone the streetmerchant github.
  2. Configure the dotenv and global.proxies file with valid proxies
  3. Install and run: npm run start

Environment

  • OS: I've tried Windows 10 and MacOS.
  • NodeJS: I've tried NodeJS 16, and NodeJS 15.
dotenv
Nothing Particular dotenv. Any should reproduce the same result.
global.proxies
socks5://<my_username>:<my_password>@<my_secret_ip_address_1>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_2>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_3>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_4>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_5>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_6>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_7>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_8>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_9>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_10>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_11>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_12>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_13>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_14>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_15>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_16>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_17>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_18>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_19>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_20>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_21>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_22>:1085
socks5://<my_username>:<my_password>@<my_secret_ip_address_23>:1085

Logs

Using proxies with the nightly build we got net::ERR_FAILED error.

[1:38:42 AM] error :: ✖ [2/23] [newegg-ca] evga 3080 ftw3 - net::ERR_FAILED at https://www.newegg.ca/evga-geforce-rtx-3080-10g-p5-3895-kr/p/N82E16814487519
[1:38:42 AM] error :: ✖ [3/23] [canadacomputers] msi 3080 gaming x trio - net::ERR_FAILED at https://www.canadacomputers.com/product_info.php?cPath=43_557_559&item_id=181348&language=en
[1:38:42 AM] error :: ✖ [4/23] [memoryexpress] evga 3080 xc3 black - net::ERR_FAILED at https://www.memoryexpress.com/Products/MX00114094

Exactly the same config works as expected with the latest docker image

[1:47:52 AM] info :: ✖ [2/23] [memoryexpress] [gigabyte (3080)] eagle oc :: OUT OF STOCK
[1:47:52 AM] info :: ✖ [1/23] [canadacomputers] [evga (3080)] ftw3 ultra :: OUT OF STOCK

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions