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
We're using OLS in some of our cloud servers and we give our customers the choice to use it instead o Apache, which means that the web server not in use is masked via systemctl.
My problem is that, upon upgrading OLS via yum it starts unconditionally, regardless of if it was running or Apache was, which generates conflicts as it tries to bind to ports 80 and 443.
Is there a way to stop this behaviour? Is it a packaging issue? (We're using the oficial repos from LiteSpeed Tech).
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi!
We're using OLS in some of our cloud servers and we give our customers the choice to use it instead o Apache, which means that the web server not in use is masked via systemctl.
My problem is that, upon upgrading OLS via yum it starts unconditionally, regardless of if it was running or Apache was, which generates conflicts as it tries to bind to ports 80 and 443.
Is there a way to stop this behaviour? Is it a packaging issue? (We're using the oficial repos from LiteSpeed Tech).
Thanks in advance.
The text was updated successfully, but these errors were encountered: