You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use the WEBPORT variable to set a specific port (such as 5000), the container will normally provide an http interface on port 5000, but will additionally occupy port 443 for https services.
When docker uses the host network mode, if nginx is used as a reverse proxy (https), it will cause a conflict with nginx's port 443, and eventually it will be stuck in a continuous restart.
The text was updated successfully, but these errors were encountered:
This is because the latest-alpine image is built with apache2-ssl installed, which I recommend removing. Users should set up their own reverse proxy (e.g., nginx) to implement https, not librespeed. At the same time, I don't think it will be easy to use librespeed's https function.
Description
If you use the WEBPORT variable to set a specific port (such as 5000), the container will normally provide an http interface on port 5000, but will additionally occupy port 443 for https services.
When docker uses the host network mode, if nginx is used as a reverse proxy (https), it will cause a conflict with nginx's port 443, and eventually it will be stuck in a continuous restart.
The text was updated successfully, but these errors were encountered: