-
Notifications
You must be signed in to change notification settings - Fork 549
Request to support custom ssl port #5386
Comments
I thought of a compromise, but it doesn't seem to work. So I have come to seek help from the community. I turned off openpai's ssl and changed http to listen on port 8080. Now I can access http://MasterIP:8080 in the browser. Then I used the following two configurations to start a nginx service to manage ports 80 and 443. docker-compose.yml
nginx/default.conf
But, unfortunately, this does not work. The strange thing is that I only need to change 443 to another port, such as 8443, it works. I was wondering if it conflicted with pylon, Because other possible solutions, such as port forwarding, don't work either. |
Indeed, pylon occupies port 443, because this line hostPort: 443 do not in |
I modified the source code of pai in dev-box, but the above configuration file still doesn't work. It seems that there are conflicts elsewhere. |
Fixed by #5495 |
What would you like to be added:
I need openpai to support custom SSL port.
Why is this needed:
If the administrator can customize the ssl port, it will be possible to deploy multiple websites on the same master node through an additional nginx service. But now the ssl port number is designated as 443, without modifying the source code, the administrator cannot customize the ssl port. The custom ssl port is very useful, especially when the master node has sufficient computing power to deploy multiple websites.
Without this feature, how does the current module work:
ssl port must be 443.
Components that may involve changes:
hostPort: 443
basic-management-operations.md
The text was updated successfully, but these errors were encountered: