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
Many wifi spots block unusual ports like 1193. Therefore I started a second docker container on port 993. But I do not want to manage two pki aside of each other, and therefore bind mounted the pki folder into both containers.
As I had issues with crl renew...Are there any plans to easily allow multiple servers sharing one pki?
For those who are interested why I have chosen this port: I am already using port 80 for letsencrypt and 443 for nginx (port sharing is a no go). This way I was forced to move to another famous and widely used port, like 993 for IMAP over TLS. As people want to read emails, this port is likely to be opened. And using a port where TLS traffic is expected helps to avoid problems like blocked TLS traffic on port 80...really happened!
The text was updated successfully, but these errors were encountered:
Many wifi spots block unusual ports like 1193. Therefore I started a second docker container on port 993. But I do not want to manage two pki aside of each other, and therefore bind mounted the pki folder into both containers.
As I had issues with crl renew...Are there any plans to easily allow multiple servers sharing one pki?
For those who are interested why I have chosen this port:
I am already using port 80 for letsencrypt and 443 for nginx (port sharing is a no go). This way I was forced to move to another famous and widely used port, like 993 for IMAP over TLS. As people want to read emails, this port is likely to be opened. And using a port where TLS traffic is expected helps to avoid problems like blocked TLS traffic on port 80...really happened!
The text was updated successfully, but these errors were encountered: