I have tried it with Joplin Server 1.75 and the beta 2.05 but i get the same result when i attempt to login i get [image] no matter what i try its the same result [image] I am using a postgres db Any help would be appreciated

All tests were fresh installs, no residual data. Using docker

Got the same error on Server 2.0.5 when the server listened behind a reverse proxy, but the domain the server was listening on was not the domain specified in the Docker's env vars. Maybe check you have all those set correctly.

I have been using the Joplin server docker image behind an nginx reverse proxy. The last version I got to work was, 2.0.1 beta (using the SQLite db). I also had to use florider's version as the official one always started with data already in the admin account and an additional "user1" account . Even…

Yes sorry this is not currently documented, but you need to make sure that your reverse proxy passes the origin properly to the Docker image. I think it means having this on the Nginx config: proxy_set_header host $host; And this on Apache: ProxyPreserveHost on

Yep, that's it for nginx. In case it helps anyone, this works for me: server { server_name joplin.example.lol; location / { proxy_pass http://127.0.0.1:31337; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_se…

Thanks for sharing your config, the "client_max_body_size" property is important too. I guess once the server gets more stable we can put a sample Nginx and Apache config in the doc.

That we definitely should. It's always a hassle to figure out/troubleshoot when projects don't do that.

[image] laurent: Yes sorry this is not currently documented, ... [aaugh] (Server now working :slight_smile: )

In case anyone is interested this is an nginx "sites-available" reverse-proxy file that uses self-signed certs, diverts port 80 to 443, adds a bit of hardening and also logging. It does work with 2.0.6-beta. { listen 80; server_name joplin.example.lol; return 301 https://joplin.exampl…

I'm kind of screwed, I'm using IIS 8 Url Rewrite <?xml version="1.0" encoding="UTF-8"?> <configuration> <system.web> <httpRuntime requestPathInvalidCharacters="" /> <pages validateRequest="false" /> </system.web> <system.webServer> <rewrite> <rules> …

New Install - Invalid origin error

Support

BigWebstas 10 June 2021 17:57 12

Even if i try to hit it directly "http://10.2.0.140:22300" i get Invalid origin

Topic		Replies	Views
Joplin Server Setup - Invalid origin Support	12	10239	30 June 2021
Invalid Origin error on the server Support	1	1307	29 March 2025
Joplin server and Docker error message Development	2	1161	4 October 2023
Joplin Server is not working Support	2	6019	7 January 2024
Joplin Server behind Nginx + home router custom HTTPS port gives “Invalid origin” Support	1	364	7 November 2025

New Install - Invalid origin error

Related topics