I’ve been trying to host passbolt local on my Fedora server for a few hours now.
In doing so I am following the instructions from networkchuck.
So I have 3 docker containers (mariadb, passbolt and traefik). All 3 are running properly. The only difference from the video is that for APP_FULL_BASE_URL, traefik.http.routers.passbolt-http.rule and traefik.http.routers.passbolt-https.rule are pointing to a subdomain. so like this https://passbolt.mydomain.tech
When I create the admin account and open the generated link, it also comes up with the correct subdomain (passbolt.mydomain.tech)
What could be the reason that it responds to me with ERR_CONNECTION_REFUSED every time on the subdomain?
“At this point, you should have a working docker setup running on the latest tag. However, it is recommended that users [pull the tags pointing to specific passbolt versions. The current version is 3.12.2
If you have already verified that your firewall is disabled and your containers are running properly, there could be a few other reasons why you are receiving an ERR_CONNECTION_REFUSED error when accessing your Passbolt instance through your subdomain.
Here are some steps you can take to troubleshoot the issue:
Check if your DNS settings are correct: Make sure that the DNS settings for your subdomain are pointing to the correct IP address of your Fedora server. You can use the nslookup or dig commands to verify that your subdomain is resolving to the correct IP address.
Check if your Traefik configuration is correct: Double-check your Traefik configuration to ensure that you have set up the correct routing rules for your Passbolt container. Specifically, check the traefik.http.routers.passbolt-http.rule and traefik.http.routers.passbolt-https.rule settings to ensure they are pointing to the correct subdomain. You can also check the Traefik logs to see if there are any errors related to routing.
Check if your SSL certificate is valid: If you are using SSL for your Passbolt instance, make sure that your SSL certificate is valid and that it is installed correctly on your server. You can use tools like openssl to verify the validity of your SSL certificate.
Check if your Passbolt container is listening on the correct port: Verify that your Passbolt container is listening on the correct port (usually port 80 or 443 for HTTP/HTTPS traffic). You can use the docker ps command to check if your container is listening on the correct port.
Check if there are any other services running on the same port: Make sure that there are no other services running on the same port as your Passbolt container. You can use tools like netstat to check if there are any other services listening on the same port.