Closed sebastian-burlacu closed 2 years ago
Update: removing /joplin from APP_BASE_URL fixes this issue. So this might just be a documentation thing.
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.
Here is my work nginx configuration for your reference:
location /joplin/ {
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://localhost:22300/;
}
Update: removing /joplin from APP_BASE_URL fixes this issue. So this might just be a documentation thing.
Thank you. This fixed it for me.
Using http, not https. I'd expect if I put /joplin in APP_BASE_URL in .env, it should use it, but it doesn't work. Not sure what's happening here.
Here are docker commands to create postgres and joplin containers:
And here are the uncommented parts of the .env file:
Environment
Joplin version: 2.7.4 Platform: server OS specifics: Ubuntu 18.04
Log file
Failed navigation to http://server:22300/joplin/login
Successful navigation to http://server:22300/login still shows other pieces of the site not working.