Receiving an error message on a new configuration on Ubuntu.

Hi there., based on the error you are seeing it looks like Connect cannot find your 1password-credentials.json file that you generated when created your connect instance. Can you confirm that your credentials file is located in the same directory as the directory you are running docker-compose up from?

Hi Jillian, thank you for the quick response!

Here is the output of trying to run it from the command line, starting with the directory that I'm in and the files that are in the directory with me (the credentials file is located in the same directory as I'm running and the compose file is there as well, as you can see).

~/1pass$ pwd
/home/user1/1pass
~/1pass$ ls -l
total 8
-rw-rw-rw- 1 user1 user1 1133 May 26 09:23 1password-credentials.json
-rw-rw-rw- 1 user1 user1 494 May 26 10:10 docker-compose.yaml
~/1pass$ cat docker-compose.yaml
version: "3.4"

services:
op-connect-api:
image: 1password/connect-api:latest
ports:
- "8080:8080"
volumes:
- "./1password-credentials.json:/home/user1/1pass/1password-credentials.json"
- "data:/home/user1/1pass/data"
op-connect-sync:
image: 1password/connect-sync:latest
ports:
- "8081:8080"
volumes:
- "./1password-credentials.json:/home/user1/1pass/1password-credentials.json"
- "data:/home/user1/1pass/data"

volumes:
data:
~/1pass$ docker-compose up
[+] Running 3/3
✔ Network 1pass_default Created 0.3s
✔ Container 1pass-op-connect-api-1 Created 1.6s
✔ Container 1pass-op-connect-sync-1 Created 1.6s
Attaching to 1pass-op-connect-api-1, 1pass-op-connect-sync-1
1pass-op-connect-sync-1 | {"log_message":"(I) no existing database found, will initialize at /home/opuser/.op/data/1password.sqlite","timestamp":"2023-05-26T17:11:41.357203759Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) starting 1Password Connect Sync ...","timestamp":"2023-05-26T17:11:41.358970504Z","level":3}
1pass-op-connect-api-1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2023-05-26T17:11:41.44886205Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) database initialization complete","timestamp":"2023-05-26T17:11:41.623942393Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T17:11:41.62458989Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 500ms), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T17:11:41.624796776Z","level":1}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T17:11:42.125534373Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 1s), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T17:11:42.125688083Z","level":1}
1pass-op-connect-api-1 | {"log_message":"(I) no database found, will retry in 1s","timestamp":"2023-05-26T17:11:42.449427165Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(I) ### syncer credentials bootstrap ### ","timestamp":"2023-05-26T17:11:43.126850818Z","level":3}
1pass-op-connect-sync-1 | {"log_message":"(E) Server: (unable to get credentials and initialize API, retrying in 2s), Wrapped: (failed to FindCredentialsUniqueKey), failed to loadCredentialsFile: Server: (LoadLocalAuthV2 failed to credentialsDataFromDisk), open /home/opuser/.op/1password-credentials.json: no such file or directory","timestamp":"2023-05-26T17:11:43.127110892Z","level":1}
^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Running 2/2
✔ Container 1pass-op-connect-sync-1 Stopped 2.2s
✔ Container 1pass-op-connect-api-1 Stopped 2.2s
canceled
~/1pass$ op --version
2.18.0

Can anyone think of any other issues that would prevent the server from working on Linux?

I've tried installing it on a second Ubuntu server and had the exact same issue. Is there a different distro of Linux that works better for this? I'm going to look at setting it up on a windows machine now just to see if I can get it to work, but Windows is not the solution I want to use for this even if it does work. I just want to see if it can work.