aptalca
-
Posts
3,064 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by aptalca
-
You can use dnschecker.org to see propagation -
Are you using the preset proxy confs?
-
Set an A record for cdkauffmann.com and set it to your IP address
-
On the surface it looks about right. Actually you had to repeat the ssl info because it is in a different server block.
-
Glad to hear it worked
-
Go to WordPress admin, settings, general and you'll see two fields for wp address and site address. My guess is they are set up with www
-
That seems totally stock. I'm assuming your wordpress is being served in the www folder. You must have a redirect in wordpress. Did you set the website url as www.domain.com in wordpress settings? There could also be browser cache when 301 redirects are involved. Try a new browser or incognito
-
It's called default It's under /config/nginx/site-confs
-
Check your site config. You probably have a redirect somewhere
-
What php.ini did you create? Only modify the php local and restart. You don't need anything else
-
?? You didn't mention you already made changes to enable reverse proxy. That requires a whole another set of troubleshooting methods. Https is not a valid option for validation. Check the docs
-
That was an annoying forced change by letsencrypt done to reduce their server load at peak times. I guess they forgot that many people have scripts that are not run by cron. We pushed an emergency update last night to remove cert renewal during container start
-
Is wordpress set up in the letsencrypt container or are you reverse proxying? I have them set to 64MB the same way and it works
-
With letsencrypt, you're trying the https address, right? Log suggests nginx is started and there are no errors. What happens when you try to connect?
-
Make sure that your ip is set correctly on your dns provider and that there is a cname created and set up for the "server" subdomain. If all looks good, you can try stopping the letsencrypt container, create an nginx container with the same exact port mapping, and see if you can reach it through the domain and ports 80 and 443
-
Post a log
-
Do "docker ps" and post the line containing letsencrypt
-
Ipv6 is not supported in this image
-
I think you mean proxy and not redirect (they have very different meanings for webservers) If you post your config we'll take a look
-
Is the host ip/port in the proxy pass directive
-
Use only lowercase in container names otherwise nginx can't resolve them
-
No alpine package for the module
-
It seems to be an apache module? So no plans
-
That's a dns hostname resolution thing. Not nginx's fault. Use all lowercase in container names or define a network alias for the container
-
First set it to the regular bridge and set up your port forwards if you like. Save and exit. Go into the container settings one more time, change it to proxynet, don't enter an ip and hit save. Unraid doesn't recognize your proxynet as a custom bridge network (assumes it is macvlan) so if you try to change port mappings after selecting proxynet, unraid won't do it properly.
