-
Notifications
You must be signed in to change notification settings - Fork 704
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
driver failed programming external connectivity on endpoint nextcloud-aio-domaincheck #53
Comments
It is trying to start the domaincheck container here but that fails. This is probably because port 443 (which is needed by the domaincheck container) is already in use by something else. Which command did you use to start the master container? |
This is the only thing I used to start NextCloud:
Sorry need to clarify, if I use the local IP over 8080 I get prompted for the domain name. But it says 443 is unreachable.
|
Update, I can see my cert getting successfully requested but it's not letting me through on 443
Submitting the public domain name on the form that asks what the domain to use I get an HTTP 422 error in the POST request which gives an error message on the page of
I actually modified the
|
I am having similar issues: I am using port 80 and 443 already for apache. after this startup command:
I get this error message in my browser after logging in on port 8080
|
Sry but port 443 is required. See https://github.com/nextcloud/all-in-one#which-ports-are-mandatory-to-be-open |
@szaimen Why are you closing my issue? Port 443 is open for me and I'm getting port unreachable in a NAT'd environment. Can you please re-open my issue? |
So you didn't have this issue anymore? After restarting the mastercontainer and logging in? |
I still get that error without modifying the container in anyway. I don't recall at this time what triggers it but it happens when trying to walk through the setup on a NAT'd connection. |
The issue points to an already running service on port 443. Maybe you installed a webserver or snap on your ubuntu vm without knowing? |
The service running on 443 is your NextCloud docker container that handles the cert generation :) |
I think you may be confusing two different issues.
Here are POST calls for the domain I'm trying to use
We can see port 443 available just fine on the other container.
External port check from https://www.yougetsignal.com/tools/open-ports/: I can telnet to 443 fine on your container as well
2nd issue: I'm happy to do a screenshare and live debugging call to help you on these if you want. |
Honestly I don't know what the bug you are experiencing could be. I can only report that it works here and everywhere else because there would be many more people that would run into your issue if it would be really an issue on our side. The error that you get on your latest screenshot is triggered here: all-in-one/php/src/Data/ConfigurationManager.php Lines 115 to 120 in 02365fd
Maybe it helps you figure out why that seems to fail. It should actually successfully connect to the domaincheck container if your server is correctly reachable via that domain and you've correctly set up port-forwarding and co. |
Thanks, yeah, I was modifying that code earlier and I got HTTP 200s if I comment out that code and hard code the IP to be the local IP instead of the public IP but the UI isn't able to progress. |
Anyone else seeing this issue?
I just created a brand new Ubuntu 20 Server (VM running in ESXI, NAT'd to a static public IP.), installed Docker. When walking through the install instructions, port forwarding 443, 8443, and 80, installing the NextCloud container; when I log in via the LOCAL IP at 8080 over https with the admin credentials I get
The server is not reachable on Port 443.
If I follow the public doc instructions
I don't think these instructions are accurate. I can see the public port open on my public IP but visiting the public domain name via 8443 just times out.
The text was updated successfully, but these errors were encountered: