Share this post:
Responses (1)
-
Accepted Answer
Hello,
Restarting webconfig will do the trick (or a reboot too).
Too much information: basically, the webconfig engine needs to restart itself when one of these "web server aliases" (/mysql in this case) comes along. That poses a bit of a chicken/egg problem and there's some underlying voodoo to handle this scenario.
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »