It seams it doesn't work

[kostiantyn-petlia]

Hi.

I tried to use your code with my docker-compose.yml and even without any changes and it doesn't work for me on Ubuntu 20.04.
Perhaps, you could take a look at it and give me some advice? How I can debug it?

The site works well on http://my-wordpress-blog.local:8080/ Admin Dashboard shows the site not ready for HTTPS.
On https://my-wordpress-blog.local:8080/ I have the next error:
This site can’t provide a secure connection my-wordpress-blog.local sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Thank you for your time.

[vishalraj82]

By default, HTTPS works on port 443. And mind that HTTP and HTTPS will not work on same port. Try the HTTPS version without the port.

[kostiantyn-petlia]

I did that and I guess it redirects from https://my-wordpress-blog.local to https://my-wordpress-blog.local:8080.

[vishalraj82]

Can you please share the nginx configuration that you are using?

[kostiantyn-petlia]

There no changes. The same the repository has it, downloaded and ran as:
sudo docker-compose up -d
In the hosts I added "127.0.0.1 my-wordpress-blog.local".
That's why it's strange for me.

[vishalraj82]

The nginx listens only on port 80 and 443. The port 8080 is handled by wordpress docker container. I tried it and all seems to be working fine. Would it be possible for you to record a video and share the link, so that I can pin point the issue. Thank you.

[EngKhaledB]

Make sure that the site url on WordPress settings = https://my-wordpress-blog.local not https://my-wordpress-blog.local:8080
@kostiantyn-petlia
Of course you need to login to dashboard via the link: http://my-wordpress-blog.local:8080

[vishalraj82]

@EngKhaledB The whole purpose of this setup is to not use PORT and have HTTPS.

[wgroenewold]

@EngKhaledB You can go to dashboard via https://my-wordpress-blog.local/wp-admin
@kostiantyn-petlia Seems like your browser is caching something somehow. Clear all browser history and caches or try it in a private browsing window.

[KuznetsEnvy]

There seems to be missing final closing curly brace in readme.md for /proxy/conf/nginx.conf
In actual nginx.conf file from repository the curly brace is present, so docker was giving me the following error until I figured it out:

nginx | 2023/05/29 04:26:56 [emerg] 1#1: unexpected end of file, expecting "}" in /etc/nginx/nginx.conf:29
nginx | nginx: [emerg] unexpected end of file, expecting "}" in /etc/nginx/nginx.conf:29
nginx exited with code 1

[hariszaf]

Hi, I am able to do the http case but even after closing the nginx.conf curly brace, I cannot reproduce the https case.
When I initiate the container with the proxy, I still get the site under the http://my-wordpress-blog.local:8080 with no secure protocol. Any ideas..?
Thanks!