[Bug] Failed to connect #259
Labels
bug
Something isn't working
Comments
|
config/log/firefox/error.log |
|
The problem is most likely with the reverse proxy. Can you try to connect using the IP of the host running the container ? |
|
i have the same question,if i only use ip to run the container,it will work well. however i use nginx ,it will break down after i don't have any action.if i keep using it,it will keep going on normally |
|
See https://github.com/jlesage/docker-firefox?tab=readme-ov-file#reverse-proxy for Nginx config examples. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Current Behavior
I can open the login page and successfully log in, then enter the page shown in the picture。
Expected Behavior
I don't know the cause of the problem.
Steps To Reproduce
No response
Environment
Client: Docker Engine - Community
Version: 27.2.1
API version: 1.47
Go version: go1.22.7
Git commit: 9e34c9b
Built: Fri Sep 6 12:08:02 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.2.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 8b539b8
Built: Fri Sep 6 12:08:02 2024
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.7.22
GitCommit: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc:
Version: 1.1.14
GitCommit: v1.1.14-0-g2c9f560
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Web access data flow: Local browser(Firefox) --> VPS(Nginx) --> VPS(FRP Server) --> N100(FRP Client) --> Docker Firefox
VPS: Alibaba Cloud Server, OS Ubuntu
FRP: https://github.com/fatedier/frp
Container creation
Container log
Anything else?
Nginx Reverse Proxy
upstream upstream_firefox { server frps:6000 max_fails=3 fail_timeout=3s weight=10; } server { listen 80; listen [::]:80; server_name firefox.example.com; return 301 https://firefox.example.com$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; server_name firefox.example.com; add_header Strict-Transport-Security "max-age=63072000; includeSubdomains; preload"; add_header X-Frame-Options "SAMEORIGIN"; charset utf8; access_log /var/log/nginx/frps/firefox.example.com/access.log main; error_log /var/log/nginx/frps/firefox.example.com/error.log warn; location / { #proxy_next_upstream error timeout invalid_header http_500 http_503; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Connection $connection_upgrade; proxy_set_header Upgrade $http_upgrade; proxy_pass http://upstream_firefox; proxy_redirect off; #proxy_connect_timeout 86400s; #proxy_send_timeout 86400s; #proxy_read_timeout 86400s; proxy_http_version 1.1; #proxy_buffering on; #proxy_buffer_size 1024k; #proxy_buffers 32 64k; #proxy_busy_buffers_size 1024k; #proxy_temp_file_write_size 1024k; } location /websockify { proxy_pass http://upstream_firefox; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; proxy_read_timeout 86400; } # ssl on; ssl_certificate /etc/nginx/ssl/frps/firefox.example.com/cert.pem; ssl_certificate_key /etc/nginx/ssl/frps/firefox.example.com/key.pem; ssl_session_timeout 5m; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4:!DH:!DHE; ssl_prefer_server_ciphers on; }frpc
The text was updated successfully, but these errors were encountered: