-
-
Notifications
You must be signed in to change notification settings - Fork 48
Able to log in, but POST updates to syncing-server are returning 500 #79
Comments
Standard Notes syncing server logs are showing this:
|
Could you please post the complete log from the syncing-server? |
I added logs just now, do you mean more than the above? |
Yes. Ideally, the logs should include the |
|
Not sure why it is saying AWS? This is locally hosted. I am using the production flag though, if that helps. EDIT: Going back to the development tag fixes the issue. Not sure why. |
This method should not exist in |
Yep, that's the issue. Any reason why |
@karolsojko |
Application's code layer should be agnostic of infrastructure and cleanup of excessive revisions is. Not sure what you had in mind with checking if it's enabled - aren't other I think we need to update the docs that the app uses shoryuken which utilizes AWS SQS in production mode. Or provide an alternative to run jobs inline by default? What do you think? |
Yep just some solution to AWS dependence. Users shouldn't need to use AWS to self-host. Inline jobs could be a good solution. |
Hello,
I am running Standard Notes behind an nginx reverse proxy -> Standard Notes server.
I am able to authenticate and pull in notes from my Standard Notes server to the client, but about 80% of the time, it is unable to update those notes back in the server. Sometimes it works, sometimes it doesn't. The result is conflict merge issues, with notes just continuing to duplicate on my client.
The access logs for Nginx reverse proxy show 200's and then sometimes 500's, which correspond with sync failures. Error logs show nothing at all.
Any ideas?
Here's the access log sample:
Reverse proxy nginx config:
Standard Notes server systemctl service file:
The text was updated successfully, but these errors were encountered: