Closed ghost closed 9 years ago
This may be a connectivity issue between your server and the hosted verifier. If you're not already, try uncommenting the section at the bottom of syncserver.ini
that talks about using a local verifier.
It looks the above are all client-side logs, are any server-side logs generated when this error occurs?
I disabled iptables
but the problem still persists. The log file /var/log/ffsync.log
does not contain anything (despite being set in the service script). I want to use the BrowserID instance running at Mozilla, what settings should I use in the synserver.ini
file?
I want to use the BrowserID instance running at Mozilla
That should happen by default. Can you successfully make outbound connections to https://verifier.accounts.firefox.com/ from your instance?
wget https://verifier.accounts.firefox.com/ --2015-11-16 10:46:53-- https://verifier.accounts.firefox.com/
Resolving verifier.accounts.firefox.com (verifier.accounts.firefox.com)... 54.244.29.62, 54.218.68.106
Connecting to verifier.accounts.firefox.com (verifier.accounts.firefox.com)|54.244.29.62|:443... connected.
HTTP request sent, awaiting response... 405 Method Not Allowed
2015-11-16 10:46:54 ERROR 405: Method Not Allowed.
Seems to work fine, any suggestions to run firefox sync in console instead of service?
Ok, I feel fooled by Firefox. The service was never starting in the first place, and I think I got served an cached response of "it works". After rebuilding the project and starting it manually it works. Sorry for the waste of time :S
no worries, glad you were able to get it working!
Don't know how to fix this. I'm using a Firefox account in combination with my own 1.5 Sync server which worked fine on my previous VPS. The bad gateway error seems to be from my webserver, but when I go to the URL that I set in the about:config it tells me "it works" and i'm not authorised.