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.

Sign up for GitHub

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

Jump to bottom

Server setup fails on Enabling SSL with 404 #34

Closed
lgraubner opened this issue Sep 11, 2019 · 7 comments
Closed

Server setup fails on Enabling SSL with 404 #34

lgraubner opened this issue Sep 11, 2019 · 7 comments

Comments

@lgraubner
Copy link

I have a server running the caprover docker container and an root domain like captain.api.my.domainname.com with an A record *.captain.api.my.domainname.com pointing to my server.
I can access the dashboard and login.

Whenever I'm trying to run caprover serversetup it fails on "Enabling SSL" with Error: StatusCodeError: 404 - "<!doctype html>\n<html>\n\n<head>...

So basically the html output of the default page. What am I doing wrong? DNS is properly propagated.
@daniel-trevino
Copy link

Hello,

Do you also experience issues by setting up the server using the GUI instead of the CLI?

@lgraubner
Copy link
Author

I was able to enable HTTPS without any problems from the Dashboard.

@lgraubner
Copy link
Author

Oh by the way: I'm using Ubuntu 18.04 as 16.04 already reached end of life.

@iFloris iFloris mentioned this issue Sep 11, 2019
Closed
@Hazzard17h
Copy link
Contributor

I think this is a bug for root domains that start with captain.

CapRover admin dashboard (where the API is enabled, too) is deployed at captain.$rootDomain.
When you inserted the root domain, the CLI updated your instance with that value, and than created the admin domain for subsequent calls (enable https, ecc...), checking if root domain starts (after the protocol) with captain., and, if not, adding it to the provided root domain.

Ultimately, you can fix this for now by changing your root domain and DNS A record (e.g. caprover.api.my.domainname.com), or finalizing your setup from the dashboard.

@lgraubner
Copy link
Author

That's the issue. Changing the subdomain works. Thanks! :)

@githubsaturn
Copy link
Collaborator

Thanks @Hazzard17h for sorting this out. I think we should re-open and address the root cause - though it's not high priority.

@githubsaturn githubsaturn reopened this Sep 12, 2019
@Hazzard17h Hazzard17h mentioned this issue Sep 18, 2019
Merged
@githubsaturn
Copy link
Collaborator

Fixed in #33 and released as 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lgraubner @daniel-trevino @githubsaturn @Hazzard17h