OLS just stops listening to IPv6 after some time. When I restart it, it's fine again but after a day or so IPv6 on 80 and 443 isn't accessible again. Any advice on how I can diagnose this? What log should I look into? Thank you.
I'm having the same issue since a few days. (Maybe longer but didn't notice it before).
You can check the Apache error log to get more info. In my case it says that all ipv6 addresses are busy/occupied. They are not, so I think it's an issue occuring when ols restarts "too fast" by a command called from Directadmin. Because after a manual restart it works again.
No solution found though so ideas are welcome. ��
For me also, same problem applies. OpenLiteSpeed stops listening to IPv6 after some undefined time, both on port 80 & 443.
No solution sofar.
I have installed DA through the Custombuild scripts on a fresh server (no clients at all) and the server has one IPv4 address active, and one IPv6 address.
Both addresses have initially been configured on the interface, not through DA, although ofcause both have been added to DA.
Server is a physical machine, not a VPS, with CentOS 7 installed.
Using 'evolution' skin, as Admin, clicking 'Server Manager' -> 'Custom HTTPD Configurations' and on that page clicking one of the openlitespeed.conf behind the available domains, I get to view the 'Domain Configuration' for the domains under this account, and it has a big red button 'Syntax Error' behind the 'Domain Configuration' title.
Looking through the 'Contents of the openlitespeed.conf file' I see nothing special (it's all default), but under the 'Domain Configuration' is a 'Configuration Check' check section with two highlights:
2019-09-26 10:20:03.102723 [WARN] Path for document root is not accessible: /var/www/html/domains/sharedip/
2019-09-26 10:20:03.102767 [WARN] [config:server:vhosts:vhost:[2001:41d0:2:xxxx:0:0:0:1]] configuration failed!
Since all has been freshly installed, and nothing has been edited from the defaults, this might point to something, but sofar I have been unable to understand where these warnings originate from.
So, anyone with insights in this who could share some would be welcome!