• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Plesk Nginx + docker container associated with subdomain how to expose ports to the internet

xdasty

New Pleskian
Hi Guys
I explain to you my problem,
I have a mqtt service in a docker container, with ports
80-> 8080,
1883-> 1883,
8883-> 8883,
8884-> 8884

on plesk nginx is activated in proxy mode

I have set Docker Proxy Rules, and so far it works,
https: //service.domain .com/admin
that points correctly:

the other ports are not resurrected to operate them.

But I wish it worked this way
MQTT: //service.domain.com:1883
mqtts: //service.domain.com: 8883
ws: //service.domain.com: 8884

respectively they will have to point to the docker container with the name service_mqtt at the ports
- 80
- 1883
- 8883
- 8884

I have done several searches for days on the net but, among the tons of information read,
someone has already solved this problem.
Thanks in advance
for any help or suggestions
 
Update:

on the main domain, the one with which plesk is associated works, but the goal is to reach the ports of the docker which is associated with a subdomain of any of the subscriptions.
 
Back
Top