0

My prelimanary actions:

  • setting up a ddns hostname with noip service (ok)
  • configured to automatically keep alive the association on my home router(ok)
  • installed a proxmox server v8 (ok)
  • create a lxc container with model "debian11-turnkey-wordpress" with a static IP (ok)
  • configured port forwarding 80,443 on router to point the lxc wordpress container(ok)

The current situation:

The website in lan is ok When I try to access from internet with the ddns hostname it works the first time and then goes in ssl cert error both with http/https When I try to get let's encrypt certificate with the selfconsole panel it fail in fatal error

My questions: How i can implement correctly the ssl certification in the container to use https from internet to lan container inside proxmox with a forwarding from outside to home network lan?

The configuration must be applied only on containers or there is somthing to do in general in the proxmox os, instead, to have all the newest containers ssl encrypted by default?

Improve this question
7
  • Proxmox doesn't care what you do with the container. If you've got a container running a web server then that is where you need to put your certificate. The only exception is when you are proxying on the router rather than port forwarding Commented Oct 21, 2023 at 19:01
  • Ok, so what I need to do to have a proxmox debian11-turnkey-wordpress container accesible from internet using the ddns hostname that identify my router that forward 80,443 request to it with a correct ssl encryption? Commented Oct 21, 2023 at 19:15
  • Install an SSL certificate into your container's web server Commented Oct 21, 2023 at 19:43
  • You should investigate why Lets Encrypt failed in your container - check the logs if any - did it fail due to dependency errors? Permissions? Commented Oct 21, 2023 at 19:43
  • 1
    Unless you've set up a redirect from http to https you shouldn't need a certificate to access your website on http (port 80). You can test with that. And then go and get (say) a LetsEncrypt certificate for the https service Commented Oct 21, 2023 at 20:05

1 Answer 1

Reset to default
0

The problem was a bad configuration of port 443 on the router. Problem solved.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.