Quicksetup acme "cant find solver" "firewall problem?" about quicksetup HOT 10 CLOSED

You did nothing wrong, and I'm sorry you've been fighting with this. (I edited your question to add ``` before and after code lines to make it easier for me to read.)

I'm surprised at the error: Could not find solver for: tls-alpn-01" which is being reported back to us by Let's Encrypt...

In your configuration.yaml file, have you specified your DNS domain as a simple name such as

dns_domain: my.domain.example

or does that have a scheme on it as in https://my.domain.example? This would be wrong.

Regarding VPS on Oracle cloud: we've no experience with that, so it might of course well be that that cloud is not permitting Let's Encrypt to connect back to your VPS for the http-01 challenge which it needs to verify your OwnTracks machine is actually yours ... This connection would be done on port 80.

from quicksetup.

If you attempt to connect to your OwnTracks VPS from elsewhere, say using something like the following do you see a connection refused message (expected) or something else?

curl -v http://my.domain.example

And just to be sure let me ask: does the name my.domain.example point to the address of your VPS?

from quicksetup.

Thanks for the quick response. I really apreciate your help!
Yes, the domain is set as a simple domain, just domain.de. I also checked that the domain is pointed at the public ip of the vps by pinging and searching my domain on a dns lookup. When running curl -v http://my.domain.example from my android however I get.

curl -v http://domain.de

• Could not resolve host: domain.de
• Closing connection 0
  curl: (6) Could not resolve host: domain.de
  $

Does that mean that my VPS doesnt allow connections as you suggested?

from quicksetup.

Your last comment doesn't quite compute: on the one hand you say you can resolve and ping the domain, on the other hand in the curl example you say the result is "could not resolve host". (That's what happens when one tries to obfuscate ;-)

Please double-check your details.

You can also gladly send us the actual domain name via an email to [email protected], and I'll gladly verify for you. (Please mention this issue number in the subject if you do.)

from quicksetup.

Let the record show it turns out there was a firewall blocking access to 80 and 443.

Thanks a lot for your help Jan-Piet! This will probably not be the last time you heard from me since the process of setting the apps up and working is still a long way. But thanks for now!Have a nice day

Glad you solved it.

from quicksetup.

from quicksetup.

HTTP status 405 is "method not allowed" which appears to indicate that either the server is misconfigured (not terribly likely) or something is intercepting that query.

If you followed these instructions from the Booklet that should not be occurring, as we configure for the MQTT protocol which for OwnTracks is much more capable. You would need to enable TCP port 8883 on your firewall if it is currently disabled.

from quicksetup.

from quicksetup.

from quicksetup.

The login is at https://yourdomain.example/owntracks/

from quicksetup.