Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Deployment Issue] - Self Signed Certificate and Appending Captain to Server Domain. #1970

Open
TonyGibson opened this issue Dec 27, 2023 · 5 comments

Comments

@TonyGibson
Copy link

TonyGibson commented Dec 27, 2023

Hi all!

I'm currently trying to deploy a SvelteKit application and my GitHub Actions workflow seems to be failing because it's using a self-signed Caprover certificate during the build process (first image)

During deploying I can see it's appending 'captain' to my domain like this: 'captain.buildershield.server.buildershield.com.au' whereas in the tutorial it appends his 'appname' to the domain like this: 'appname.domain.com'

I can access the domain buildershield.server.buildershield.com.au and the certificate is valid (screenshots of both domains below).

I have my A records set up for the server subdomain as so, as well as a * on the root and the domain is managed from Hostinger.

The end goal here is to have the same app (a customer specific safety portal) running on unique sub-domains for each user like this: user1.buildershield.com.au, user2.buildershield.com.au etc...

I'm completely stumped and any help is greatly appreciated :)

image image image image

image

@maietta
Copy link

maietta commented Dec 27, 2023

You have to overcome the default self signed certificate by enabling SSL for the full caprover hostname.

I don't know if the LetsEncrypt service will issue an SSL cert with hostnames multiple levels deep, but it's worth trying.

@TonyGibson
Copy link
Author

Thanks @maietta! I'm looking at switching to an alternative like Render instead where I don't need to deal with these issues haha. Leaving it here in case anyone else runs into this issue.

@TonyGibson
Copy link
Author

For full transparency, I'm not a devops guy and this was a tough intro to how hard deployment can be. Really appreciate everything that has been done in this space.

Quicl update: Deplpyed to Render in the time between this message and the previous - 5 minutes or so. Really simple, less control, way less of a headache for me as the devops noob I am haha.

@githubsaturn
Copy link
Collaborator

@TonyGibson

The first step is to fully set up your CapRover so that you can access your caprover dashboard using captain.maybe.somthing.com - have you done this step?

@githubsaturn
Copy link
Collaborator

I tried to access your domain, but I see a cloudflare error. So looks like you've jumped a few steps.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants