carlosmorgado
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by carlosmorgado
-
-
19 hours ago, aptalca said:
It is a good thing you were born with all the answers.
For the rest of us mortals that are still learning I guess this image (not a link, 'cause that might actually be productive) really might help some. But as it turns out I tried to follow this to the best of my knowledge (apparently your
On 4/25/2020 at 6:36 AM, aptalca said:Did you Google it? It tells you exactly what the issue is
means "it does not really tell you exactly what to do, but a general direction of what to do, and the rest is on you.") and I still get the same result 522 error, any ideas?
-
12 hours ago, aptalca said:
Did you Google it? It tells you exactly what the issue is
Like these:
?
-
On 4/22/2020 at 12:53 PM, carlosmorgado said:
So what I found out is that the network I created with the
docker network create
command doesn't have access to the outside. Now I am not sure how to solve this
So I decided to do the configuration with DNS validation and redone deleted the docker image which fixed the connection problem, now my only problem is that I allways get 522 nextcloud
-
7 hours ago, aptalca said:
You need to tell curl to follow redirects
So what I found out is that the network I created with the
docker network create
command doesn't have access to the outside. Now I am not sure how to solve this
-
4 hours ago, aptalca said:
Your issues are with "outgoing" connections, not incoming. That's why I suggested dns
So I entered the console of the container and tested the following (this url was the one mentioned in the logs):
root@168ecbf2d373:/# curl acme-v02.api.letsencrypt.org 443 <html> <head><title>301 Moved Permanently</title></head> <body> <center><h1>301 Moved Permanently</h1></center> <hr><center>nginx</center> </body> </html> curl: (7) Couldn't connect to server
-
9 hours ago, aptalca said:
Did you confirm it's not dns or networking issues?
Yes, I just configured those ports on other services on unraid (for test purposes) and was able to access them from outside the network, using the domain I configured.
-
23 hours ago, aptalca said:
You have networking or dns issues. The container cannot reach out to letsencrypt servers. Check your dns, turn off pihole or whatever else blocker you may be using.
do you have anyother guess?
-
3 minutes ago, aptalca said:
You have networking or dns issues. The container cannot reach out to letsencrypt servers. Check your dns, turn off pihole or whatever else blocker you may be using.
I don't have any blocker running, and from what I see in my router everything is ok
-
Hey guys I've been trying to get this to work, but was not sucssefull.
I have the following log:
And the following config:
Hope you guys can help
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
in Docker Containers
Posted
By enable caching do you mean the orange cloud? 'Cause if so when I disable it I get
I tried enabling strict mode as someone else suggested in another post, same result, even though I am using dns validation and in the guide share some pages ago said I wouldn't need to port forward port 80 I just tried, same result.