Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox 108.0 Socks5 proxy has stopped working

more options

Hi,

I have for some time (over a year) been using a remote server as a SOCKS5 proxy for Firefox so I can bypass my local ISPs filtering.

The proxy connection is setup using an SSH tunnel like this:

ssh -D 8080 -q -C -N -f root@<remote server> That sets up port 8080 on my local machine to listen for connections which will be forwarded to ssh on the remote server acts as aSOCKS4/SOCKS5 proxy.

    -D [bind_address:]port
            Specifies a local “dynamic” application-level port forwarding.  This works by allocating a socket
            to listen to port on the local side, optionally bound to the specified bind_address.  Whenever a
            connection is made to this port, the connection is forwarded over the secure channel, and the
            application protocol is then used to determine where to connect to from the remote machine. 
            Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS
            server. 

Tried it today and it doesn't work any more. I've attached a picture of my Firefox Proxy settings and a picture of the Firefox version I am currently running. plus a picture of the error I get when I try to access the BBC website using Firefox via the proxy.

I've tried all combinations of "Proxy DNS when using SOCKS v5" and "Enable DNS over HTTPS" with no effect. I've also tried it from "Troubleshooting Mode" and the same thing happens.

I also tried accessing https://www.bbc.co.uk through the same proxy by using the command:

curl --silent --location --socks5 localhost:8080 https://www.bbc.co.uk

and it worked perfectly.

I'd be grateful if you could have a look at it and let me know what is wrong.

Thanks, Alan

Hi, I have for some time (over a year) been using a remote server as a SOCKS5 proxy for Firefox so I can bypass my local ISPs filtering. The proxy connection is setup using an SSH tunnel like this: '''ssh -D 8080 -q -C -N -f root@<remote server> ''' That sets up port 8080 on my local machine to listen for connections which will be forwarded to ssh on the remote server acts as aSOCKS4/SOCKS5 proxy. -D [bind_address:]port Specifies a local “dynamic” application-level port forwarding. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connection is forwarded over the secure channel, and the application protocol is then used to determine where to connect to from the remote machine. Currently the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server. Tried it today and it doesn't work any more. I've attached a picture of my Firefox Proxy settings and a picture of the Firefox version I am currently running. plus a picture of the error I get when I try to access the BBC website using Firefox via the proxy. I've tried all combinations of "Proxy DNS when using SOCKS v5" and "Enable DNS over HTTPS" with no effect. I've also tried it from "Troubleshooting Mode" and the same thing happens. I also tried accessing https://www.bbc.co.uk through the same proxy by using the command: '''curl --silent --location --socks5 localhost:8080 https://www.bbc.co.uk''' and it worked perfectly. I'd be grateful if you could have a look at it and let me know what is wrong. Thanks, Alan
첨부된 스크린샷

선택된 해결법

Panic over. Today's Windows Update reboot seems to have fixed the issue for me. Sorry to have wasted anyone's time.

Regards, Alan

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (1)

more options

선택된 해결법

Panic over. Today's Windows Update reboot seems to have fixed the issue for me. Sorry to have wasted anyone's time.

Regards, Alan