Discussed in #12444
Originally posted by roswitina March 1, 2026
I installed OpenArchiver using the script (bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/open-archiver.sh)"). Everything went smoothly.
However, according to the OpenArchiver instructions, the first login should refer to the directory http://IP:3000/setup. This did not happen, and I only saw http://IP:3000/login.
I couldn't log in (because no user had been created).
Excerpt from the Open-Archiover user guide
https://docs.openarchiver.com/user-guides/installation.html
- Access the Application
Once the services are running, you can access the Open Archiver web interface by navigating to http://localhost:3000 in your web browser.
Upon first visit, you will be redirected to the /setup page where you can set up your admin account. Make sure you are the first person who accesses the instance.
If you are not redirected to the /setup page but instead see the login page, there might be something wrong with the database. Restart the service and try again.
Discussed in #12444
Originally posted by roswitina March 1, 2026
I installed OpenArchiver using the script (bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/open-archiver.sh)"). Everything went smoothly.
However, according to the OpenArchiver instructions, the first login should refer to the directory http://IP:3000/setup. This did not happen, and I only saw http://IP:3000/login.
I couldn't log in (because no user had been created).
Excerpt from the Open-Archiover user guide
https://docs.openarchiver.com/user-guides/installation.html
Once the services are running, you can access the Open Archiver web interface by navigating to http://localhost:3000 in your web browser.
Upon first visit, you will be redirected to the /setup page where you can set up your admin account. Make sure you are the first person who accesses the instance.
If you are not redirected to the /setup page but instead see the login page, there might be something wrong with the database. Restart the service and try again.