Error running Joplin Server on RPi

Support
1

I have try it in Pi3 and Pi4, which have those issue
app_1 | standard_init_linux.go:219: exec user process caused: exec format error

and then
f9af1a9882ed florider89/joplin-server:latest "docker-entrypoint.s…" 2 minutes ago Restarting (1) 5 seconds ago server-v164_app_1

docker -v
Docker version 20.10.2, build 2291f61

uname -a
Linux joplinpi 5.4.83-v7l+ #1379 SMP Mon Dec 14 13:11:54 GMT 2020 armv7l GNU/Linux

2

This is a 32bit kernel, thus it doesn't support arm64. The Raspberry Pi will need to run a 64bit kernel to use the image.

Also, as mentioned above, you'll have to try the master tag for now. latest currently does not have a arm64 build.

3

OK, let me switch to Ubuntu Server 20.04.1 64-bit and feedback.

5

I got some issue after test new server in RPi.

1, Can't login after change password for "admin@localhost"

Invalid username or password
Error: Invalid username or password
at SessionModel.<anonymous> (/home/joplin/packages/server/src/models/SessionModel.ts:28:20)
at Generator.next (<anonymous>)
at fulfilled (/home/joplin/packages/server/dist/models/SessionModel.js:5:58)

2, In App Check synchronization configuration after setup Joplin Server as sync target, it can't use created username and password.

Error. Please check that URL, username, password, etc. are correct and that the sync target is accessible. The reported error was:

POST api/sessions: Unknown error (400): <!doctype html> <html> <head> <meta charset="utf-8"> 
<link rel="stylesheet" href="http://10.0.1.251:22300/css/bulma.min.css" crossorigin="anonymous"> 
<link rel="stylesheet" href="http://10.0.1.251:22300/css/bulma-prefers-dark.min.css" crossorigin="anonymous"> 
<link rel="stylesheet" href="http://10.0.1.251:22300/css/main.css" crossorigin="anonymous"> 
<link rel="stylesheet" href="http://10.0.1.251:22300/css/fontawesome/css/all.min.css" crossorigin="anonymous">
 <script src="http://10.0.1.251:22300/js/main.js"></script> </head> 
<body class="page-error"> <main class="main"> <section class="section"> 
<div class="container"> <div class="notification is-danger"> Not allowed: POST </div> <p>
<a href="http://10.0.1.251:22300/login">Back to the login page</a></p> </div> </div> </main> </body> </html> (Code 400)

3, I use 10.0.1.251 as RPi IP address, add 22300 and /joplin to different config file, I am very confused. Better use uniform config for all of them.
In Joplin App, Joplin Server URL: http://10.0.1.251:22300/joplin
In docker-compose.yml,

APP_BASE_URL=http://10.0.1.251:22300
ports:
    - "22300:22300"

In nginx,

location /joplin {
            proxy_pass http://localhost:22300;
    }
6

@lovejoplin, I've moved your topic here as the main one should not be for support requests.

7

For the APP_BASE_URL, you should use whatever the address will be through the proxy. So in your case that would be http://your-nginx-webserver/joplin.

Regarding the login, what storage backend are you using? Are you using the PostgreSQL backend? I haven't used the SQLite backend so can't give feedback on that. I haven't encountered any issues with the Postgres one. I use a second user I created for my Joplin syncs.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.