-
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug:/Enhancement:/Feature Request: "No server connection. Retry in 5s..." #27
Comments
Literally the first sentence in the docs in section HTTP-Server:
PairDrop is also working without setting up the header but than all connected clients are shown to everybody as they all seem to have the same IP address. Probably this happens because your HTTP server does not route your websocket requests correctly. Therefore, those requests fail and the client shows a message that the server is not reachable. Be sure that websocket requests (wss) that are all pointing to Be sure to follow the documention and have a look at the Apache configuration example: https://github.com/schlagmichdoch/PairDrop/blob/master/docs/host-your-own.md#using-apache
|
Probably duplicate of #24 |
As I said, I use Caddy. I don't use Apache. And I've rules set to upgrade to https. Also, the thing about X-Forwarded-For was an assumption because it was the only variable in my testing that changed / was not already set. And literally the last sentence: "It also doesn't seem to work even with X-Forwarded-For set. Unless I got the synthax wrong for Caddy proxy, because there is only a description for Nginx and Apache unfortunately." I mean, it doesn't help anybody when you just copy paste this, set it to "duplicate" and call it a day. Because #24 has nothing to do with Caddy. |
HTTP to HTTPS Redirect should be fine. Can you check whether this is implemented correctly? A websocket request (wss://) should not be redirected to https. In the network tab in the developer tools if your browser you can check the answer of your request to I don’t know anything about caddy. If you provide your current caddy configuration for PairDrop I can have a look though |
btw. I see the same errors in the browser console even when using https://pairdrop.net - I hope tis not a browser extension, could someone check their browser console please? |
I pushed some stability fixes in the last 2 weeks. Do these issues persist? |
Those probs seem gone for me now, thanks. |
Awesome! @halictuz what about you? |
Describe the bug
No server connection. Retry in 5s...
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect it to work even if "X-Forwarded-For" is not set. Or at least have the guide reflect that it wouldn't work at all without it.
Screenshots
https://ibb.co/VSFJYpZ
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
It also doesn't seem to work even with X-Forwarded-For set. Unless I got the synthax wrong for Caddy proxy, because there is only a description for Nginx and Apache unfortunately.
The text was updated successfully, but these errors were encountered: