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

Can't access Caprover Dashboard #752

Closed
dixytudla opened this issue Jul 8, 2020 · 2 comments
Closed

Can't access Caprover Dashboard #752

dixytudla opened this issue Jul 8, 2020 · 2 comments

Comments

@dixytudla
Copy link

IMPORTANT: This is a bug report. If you are having problem with deploying a particular app use the deployment issue type.

If you are having problems with deploying a particular app using a customized dockerfile - please change your questions to Dockerfile and post it where appropriate such as StackOverflow. This is a Docker question, not a CapRover specific issue.


What is the problem?
Hi Everyone,

Super noob question. Sorry if it sounds silly but I'm really new to this. Hope someone can help. I installed caprover through digital ocean successfully. I was able to access the dashboard until yesterday but now it's giving me "This site can’t provide a secure connection" error. I think it may have been from allowing the Force HTTPS option. I enabled this to allow my Facebook app to get verified.

Is there a way to disable the Force HTTPS option through an SSH connection? I appreciate you guys pointing me to the right direction. Looking forward to any help. Thanks.

If applicable, content of captain-definition file:

Steps to reproduce the problem:

  1. Go to http://:3000 on an internet browser
  2. "This site can’t provide a secure connection" pops up

Answers to the following questions where applicable:

  • Your OS and version? : Ubuntu 18.04
  • RAM? Digitalocean VM
@githubsaturn
Copy link
Collaborator

Did you assign a root domain to your app? If you enabled HTTPS, it means you have. In that case access your dashboard from captain.root.domain.com. Avoid using port 3000.

Feel free to comment if you still have questions.

@dixytudla
Copy link
Author

dixytudla commented Jul 9, 2020 via email

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

No branches or pull requests

2 participants