choosing to port 443 (or the one set with the -sp option) of the device upduck runs on. This external chosen port you set in the router must be put after the DuckDNS URL, e.g. https://mysite.duckdns.org:525/ for port 525. If you're not sure about how this works, search ...
I now try to create a new with $ nextcloud.enable-https lets-encrypt. It says that it can not resolve a domain name and there’s no valid IP address found for my domain. All is set up in my router and my webhost and is working. I can connect thro… You can also search the ...
If I try to openhttp://smash-the-like.duckdns.orgthe request will be converted to secure https connection and I will open my Home Assistant. This is very convenient as it will not matter whether you typehttporhttpswhen you try to reach your Home Assistant from the outside. If from my...
Sorry, crazy things going on in my life. All I did was go to my Domain/DNS host and have it point my 'A' record to the IP address of my DuckDNS IP. But truthfully, not sure if that fixed the issue or not. It could very well be that I got it to work with the previous vers...
But are the ipv4 and ipv6 options working for you? It does not work for me. Config: lets_encrypt: accept_terms: true certfile: fullchain.pem keyfile: privkey.pem token: token domains: - mydomainname.duckdns.org aliases: [] seconds: 300 ipv4: 'https://ipv4.text.wtfismyip.com/' ...
* * It looks like you're running dnscat2 with the system DNS server, * and no domain name!* * That's cool, I'm not going to stop you, but the odds are really, * really high that this won't work. You either need to provide a * domain to use DNS resolution (requires an ...
It is meant for quickly sharing static files beyond your local network over an HTTPS connection but can also be used within your local network (without HTTPS). Disclaimer: This project has no affiliation with DuckDNS or Let's Encrypt and is not endorsed or supported by them. Disclaimer: ...