-
Notifications
You must be signed in to change notification settings - Fork 37
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
Server Issues when benig an Nginx Reverse Proxy #97
Comments
Aha, a discovery. I paused the code on the broken section of TiddlyWebAdaptor and found that is expecting the header Etag to be on the response for the StoryList. This is present on the Localhost version
But not on the Hosted version 🤔
No idea where to go from here, but at least we know this is the error that is occurring. I suppose this is probably not the fault of TiddlyServer 😞 😅 any helpful advice appreciated, still |
These links might help. The problem you're experiencing is related to NGINX reverse proxy. You normally need to set which headers get forwarded. http://nginx.org/en/docs/http/ngx_http_proxy_module.html http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass_header |
Apologies for the late reply. Those links were indeed helpful, but seem to link to an older version of nginx. This link was more useful https://nginx.org/en/docs/http/ngx_http_core_module.html#etag but in the end I still have not fixed this issue 😞 I have seen many instances of people exposing their TiddlyWiki to the world via an Nginx reverse proxy and Let's Encrypt for the SSL, and they seemed to have no problems with these headers disappearing. But none with TiddlyServer. I will try doing it without TiddlyServer tomorrow, and see what happens. |
Solved! Adding Etag required to the Putsaver (I did not see that option beforehand) got it working in an Incognito, and it turned out one of my extensions ClearUrls was removing Etag too! Double issue, but ll fixed now. Thanks for the help mate. |
@ohare93 , also, it's better to open a new issue for a new or only partially related problem. It helps to keep things simpler and I still get notified the same.
Originally posted by @Arlen22 in #72 (comment)
Alright here it is. Original comment:
To which you had the good insight:
So I looked at the network of both localhost and the hosted version, and both are returning 404 on OPTION and HEADERS for their respective urls.
Localhost:
Hosted:
It doesn't seem to be the issue, as localhost is not experiencing anything abnormal. The only other differences I can see are that:
If there's any other info I can provide that could help anyone help me, just say the word 👍
The text was updated successfully, but these errors were encountered: