Hi, I have an Apache proxy server and 3 ejbca servers. The ejbca servers have mariadb installed and replicate simultaneously with galera. I installed ejbca with docker on the first server and was able to access the admin panel. No errors in the logs. Then I installed ejbca with docker on the second server, and tried to access ejbca admin on the second server but hit a 404. The first server also started to give a 404 immediately after even though it was working just fine before. Stoping the docker containers and restarting still results in a 404. Im assuming the database is corrupted although the logs look fine. No errors.
When creating the dbs I followed the installation docs and made a ejbca user and database. I gave the ejbca user access on all ports.
Im wondering how to proceed. Has anyone tried HA style ejbca with docker and galera before?
The docker compose looks like this (the values change slightly for each server):
Yes, using a Galera cluster is extremely common. It's a base component of the Keyfactor HW and SW Appliances. There are hundreds of Galera cluster installations out there.
There should be logs somewhere. A 404 doesn't occur unless yo use the wrong URL, or something failed to deploy, and failed deployments will be visible in the log.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With regards to a docker installation, is docker compose logs -f the only way to view logs in this case? This show the server.log in the standalone directory, but they are not showing anything pertinent. Are there other logs? Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok sorry I was so used to the normal admin portal link in a traditional ejbca installtion using the 8443 port that i kept trying to visit that. The docker link for some reason is just https://myip/ejbca/adminweb without the 8443. Sorry.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I have an Apache proxy server and 3 ejbca servers. The ejbca servers have mariadb installed and replicate simultaneously with galera. I installed ejbca with docker on the first server and was able to access the admin panel. No errors in the logs. Then I installed ejbca with docker on the second server, and tried to access ejbca admin on the second server but hit a 404. The first server also started to give a 404 immediately after even though it was working just fine before. Stoping the docker containers and restarting still results in a 404. Im assuming the database is corrupted although the logs look fine. No errors.
When creating the dbs I followed the installation docs and made a ejbca user and database. I gave the ejbca user access on all ports.
Im wondering how to proceed. Has anyone tried HA style ejbca with docker and galera before?
The docker compose looks like this (the values change slightly for each server):
version: '3'
networks:
access-bridge:
driver: bridge
application-bridge:
driver: bridge
services:
ejbca-node1:
hostname: myname
container_name: myname
image: keyfactor/ejbca-ce:latest
networks:
- access-bridge
- application-bridge
environment:
- DATABASE_JDBC_URL=jdbc:mariadb://myip:3306/ejbca?characterEncoding=UTF-8&user=myuser&password=mypass
- LOG_LEVEL_APP=INFO
- LOG_LEVEL_SERVER=INFO
- TLS_SETUP_ENABLED=simple
ports:
- "80:8080"
- "443:8443"
Last edit: Maxwell Chandler 2023-12-12
Yes, using a Galera cluster is extremely common. It's a base component of the Keyfactor HW and SW Appliances. There are hundreds of Galera cluster installations out there.
There should be logs somewhere. A 404 doesn't occur unless yo use the wrong URL, or something failed to deploy, and failed deployments will be visible in the log.
Hi Tomas,
With regards to a docker installation, is
docker compose logs -fthe only way to view logs in this case? This show the server.log in the standalone directory, but they are not showing anything pertinent. Are there other logs? Thanks!Ok sorry I was so used to the normal admin portal link in a traditional ejbca installtion using the 8443 port that i kept trying to visit that. The docker link for some reason is just https://myip/ejbca/adminweb without the 8443. Sorry.