You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I ssh into the pi and run curl http://localhost:8090 I get the html response of the login page as expected but if I try to access it from another machine using the local ip of the pi curl http://x.x.x.x:8090/ I get curl: (28) Failed to connect to x.x.x.x port 8090 after 133430 ms: Couldn't connect to server
Other docker services running on the pi are accessible over the local network with no issues so I assume this is due the the vpn. Can anyone point me in the right direction to resolve this?
Code of Conduct & PII Redaction
I have verified that this feature request is not a duplicate and is not not addressed by the FAQ and Troubleshooting.
This is not a bug report or feature request.
I agree to follow this project's Code of Conduct.
I have removed any sensitive personally identifying information(PII) and secrets from in this issue report.
The text was updated successfully, but these errors were encountered:
I tried very similar docker compose file and it works fine, I can access web port 8080 from an other PC browser. Also I can confirm VPN is used in torrent traffic. The compose file I used is like this:
Version
linuxserver/qbittorrent@sha256:fdbd674da0d9e676b37e7c5d3fa8189e5ec0b7d507549d80d9bc46e95db7875a
Support Request
I have the configuration running on a headless pi 4 successfully:
If I ssh into the pi and run
curl http://localhost:8090
I get the html response of the login page as expected but if I try to access it from another machine using the local ip of the picurl http://x.x.x.x:8090/
I getcurl: (28) Failed to connect to x.x.x.x port 8090 after 133430 ms: Couldn't connect to server
Other docker services running on the pi are accessible over the local network with no issues so I assume this is due the the vpn. Can anyone point me in the right direction to resolve this?
Code of Conduct & PII Redaction
The text was updated successfully, but these errors were encountered: