[Bug]: after install Docker, I can't login(what is default admin user? pw?)

[kelvinks]

Issue Description

Thank you for creating the OpenSign program.

I successfully installed and ran it using Docker, but I encountered an issue.

According to the YouTube video, after installation, the first time you access the browser, a page to create an administrator should appear. However, I was taken directly to the login page instead. So, I sawed the video and accessed the /addadmin URL, but it said that an administrator had already been created.

If the default administrator is created during the installation process, I think this should be clearly communicated.

Expected Behavior

No response

Current Behavior

No response

Steps to reproduce

No response

Screenshots of the issue(optional)

No response

Operating System [e.g. MacOS Sonoma 14.1, Windows 11]

Linux System (Synology Nas)

What browsers are you seeing the problem on?

Chrome

What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]

latest docker image

What environment are you seeing the problem on?

No response

Please check the boxes that apply to this issue report.

• I have searched the existing issues & discussions to make sure that this is not a duplicate.

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the existing issues & discussions to make sure that this is not a duplicate.

[GrzegorzKwasniewski7]

@kelvinks I had exactly same issue. I tried to run it in Docker and got redirected to login page. However I downloaded repo and run: npm run build - that started the app with /addadmin. I got MongoDB configured on Docker and I run locally OpenSign server on: 8080. (you need to configure .env as well)

[cs35-owncloud]

Hello everyone,
same here, I tried looking in the mongo database but couldn't find anything useful yet.

[cs35-owncloud]

Btw I tried this: #1237
But the URL /signup is always a 404.

[andrew-opensignlabs]

/signup route is not available on self-hosted version. You can only add users from admin login.

How many users do you see in your _Users class? Ideally there should be no users if you are expecting a redirect to "/addadmin" because that happens only for fresh installations that dont have any user.

[cs35-owncloud]

Hello, thanks for your answer, I might be wrong checking this way, feel free to point me to the right way

test> use OpenSignDB
switched to db OpenSignDB
OpenSignDB> show collections
_Idempotency
_Role
_SCHEMA
_User
Migration
OpenSignDB> db.getCollection('_User').find({}).pretty()

It seems there is no one.

P.S: and the /addadmin says there is already an admin, but I have none since it's a fresh install

[indra-yana]

Same issue! currently I fresh install OpenSign on my linux ubuntu machine and if I open in chromium browser like opera, chrome, edge the home page says: "Unable to connect to the OpenSign server. bla bla blaaa" but if I open in Firefox the page is shown but not redirect me to /addadmin page. I was change any port, any base url, keep it by default and more, but nothing works! only waste my day.

very strange behavior.

[cs35-owncloud]

Hello everyone,

I had it running, in my case, I had set a specific string for REACT_APP_APPID / APP_ID. By reading the doc "A 12 character long random app identifier. The value of this should be same as REACT_APP_APPID which is a variable used by Frontend React App." I assumed one had to change it, but once I set it back to opensign it worked ...
You also have to wait a looooong time for the server to start up (around 2 minutes), wait to see this:

opensign-server running on port 8080.
Command output: 
Parse DBTool v1.2.0 - Parse server tool for data migration and seeding.

Run migration on parse-server at http://localhost:8080/app

 INFO  No migrations were executed, database schema was already up to date.

 SUCCESS  Successfully run migrations.


 INFO  No migrations were executed, database schema was already up to date.
 SUCCESS  Successfully ran indexed migrations directly on db.

[nfodor]

Same issue, no way to make it work, using our own database url that works with other nodejs app and no error logged with docker compose logs -f.
Lost about an hour so far, will now look for alternatives since i need to post an NDA tonight.

[maneeshsethi]

Same issue for me, both attempting an install on a headless server with a domain, and an attempt selfhosted on ubuntu.

It actually did open the correct /addadmin url the first time I attempted on Mac local install. But I turned off the docker container and restarted it, and it failed again.

[emorgan33]

I also have this issue. Fresh install self-hosted Docker is asking for email/password.

I ran it using this command: export HOST_URL=https://opensign.yourdomain.com && curl --remote-name-all https://raw.githubusercontent.com/OpenSignLabs/OpenSign/main/docker-compose.yml https://raw.githubusercontent.com/OpenSignLabs/OpenSign/main/Caddyfile https://raw.githubusercontent.com/OpenSignLabs/OpenSign/main/.env.local_dev && mv .env.local_dev .env.prod && docker compose up --force-recreate

[KnightBoemund]

Same issue here.
The problem was the mongodb container. The logs said:

WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that!
  see https://jira.mongodb.org/browse/SERVER-54407
  see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2
  see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814

I use docker on a vm in a proxmox cluster. Here you need to change the cpu type to host.
In a VMware environment it works too. But before you need to enable the proper option in the CPU Feature Set:
Advanced Vector Extensions (AVX) cpuid.AVX Val:1

[nfodor]

Yes Mongo works only on Intel with AVX so you could use ferretdb that is a mongodb layer on top of postgres and more and that will favor a larger user base... He is BCCed so it does not mess up with github email handling...

…

On Mar 12, 2025, at 08:15, KnightBoemund ***@***.***> wrote: KnightBoemund left a comment (OpenSignLabs/OpenSign#1578) Same issue here. The problem was the mongodb container. The logs said: WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also docker-library/mongo#485 (comment) I use docker on a vm in a proxmox cluster. Here you need to change the cpu type to host. In a VMware environment it works too. But before you need to enable the proper option in the CPU Feature Set: Advanced Vector Extensions (AVX) cpuid.AVX Val:1 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented. <#1578 (comment)> <https://github.com/notifications/unsubscribe-auth/AAGWLFNJIB54BCQPQC4ZPUT2UBFSJAVCNFSM6AAAAABXHNV5AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYGIZTGNBYG4> KnightBoemund left a comment (OpenSignLabs/OpenSign#1578) <#1578 (comment)> Same issue here. The problem was the mongodb container. The logs said: WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also docker-library/mongo#485 (comment) I use docker on a vm in a proxmox cluster. Here you need to change the cpu type to host. In a VMware environment it works too. But before you need to enable the proper option in the CPU Feature Set: Advanced Vector Extensions (AVX) cpuid.AVX Val:1 — Reply to this email directly, view it on GitHub <#1578 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGWLFNJIB54BCQPQC4ZPUT2UBFSJAVCNFSM6AAAAABXHNV5AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJYGIZTGNBYG4>. You are receiving this because you commented.