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
502 Bad Gateway right now! #10414
Comments
I'm also seeing the 502 Bad Gateway during sync with hosted Joplin Cloud on both of my Macs and my Android phone. |
Apparently resolved on all systems now. Thanks to any programmer-intervenor or, in the absence of such on this occasion, the divine or chaotic forces that either favoured or arbitrarily permitted a resumption of ordinary service! |
Apologies for these issues in the past few days. We're investigating a few solutions to prevent this from happening again |
Thank you so much!
…On Tue, 14 May 2024 at 01:27, Laurent Cozic ***@***.***> wrote:
Apologies for these issues in the past few days. We're investigating a few
solutions to prevent this from happening again
—
Reply to this email directly, view it on GitHub
<#10414 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A2UBCABFGRUUY3ECLJCOX3LZCFK7PAVCNFSM6AAAAABHNUSQBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBZGA2TANZQGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Best regards
Tim Morgan
Mobile: 07793 60 88 77
33 Enfield Cloisters
Fanshaw Street
Hoxton
London
N1 6LD
United Kingdom
|
@laurent22 Just a heads up, it's doing the 502 error again on sync from MacOS & Android. |
Good morning,
I'm getting the same error message on all platforms at 07:06:10, UK time.
|
Operating system
Windows
Joplin version
Joplin for Desktop 2.14.20
Desktop version info
I'm getting 502 Bad Gateway on the desktop app, from saved links to published notes, from the IOS app.
Can this be fixed? Thanks!
Current behaviour
I try to synchronise. Synchronisation fails.
E.g. error:
Completed: 08/05/2024 21:30 (22s)
Last error: Error: Error 502 Bad Gateway: <title>502 Bad Gateway</title>
502 Bad Gateway
nginx/1.18.0 (Ubuntu)
Expected behaviour
[Normal connection]
Logs
No response
The text was updated successfully, but these errors were encountered: