The proxy doesn't work

[j8xx]

Describe the bug
hello
when I am connected to the proxy(without being connected to tor) my computer thinks I'm offline and refuses to open any websites(regardless of them being blocked sites or not).

when I am connected to tor and according to the windows settings also connected to the proxy, the proxy doesn't work. as in I cant open block sites(ERR_SOCKS_CONNECTION_FAILED or This site can’t be reached or ERR_FAILED) also in Youtubes case specifically it just thinks I'm offline and asks me to connect to the internet.

Around three days ago everything was working perfectly, so I thought its probably due to something I changed so I reinstalled the program but it didn't seem to fix anything.

also I'm using opera gx but I also tried chrome and the problem persisted.

sorry if this is not that helpful, I'm not entirely sure what helps and what doesn't so I just pointed out all things I thought might be important

To Reproduce
Steps to reproduce the behaviour:

1. Go to Onionfruit
2. Click on Connect
3. Open a blocked website
4. ERR_SOCKS_CONNECTION_FAILED

Expected behaviour
I expected the website to load.

thanks for reading.

Screenshots

Logs
OnionFruit-2023.1.07-session2.txt

[aspriddell]

The logs have this line in which is what I guess is the issue:

2023-01-07 23:48:16 [dbg] Jan 07 23:48:16.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. [436 similar message(s) suppressed in last 300 seconds]

As you mention blocked sites, are you using a bridge to connect to tor? If you're using obfs4, I'd suggest getting some new bridge lines and trying them

[j8xx]

no actually i dont use any bridges.
on tor i used to use snowflake which worked well enough but the proxy on onionfruit made it so I didn't need to use snowflake anymore. but now even with snowflake the error still persists.

[aspriddell]

Another line from the log file is

[notice] Opened Control listener connection (ready) on 127.0.0.1:9052

I'm guessing the errors are coming from trying to connect to the control port instead of the socks port.
If you get this error again, try opening the proxy settings and manually change the port 9052 to 9051 and reload the browser.