[Solved] cPanel email autoconfig not working
- Thread starter Monarobase
- Start date
They exist, but I don't think it's them that are causing this.
The lines causing this in cPanel's apache httpd.conf are :
As you can see it doesn't use any of the above ports.
If I create one for port 80 will it cause issues with litespeed ? Shouldn't litespeed already respond to 127.0.0.1 on port 80 ?
The lines causing this in cPanel's apache httpd.conf are :
As you can see it doesn't use any of the above ports.
If I create one for port 80 will it cause issues with litespeed ? Shouldn't litespeed already respond to 127.0.0.1 on port 80 ?
please try. currently our lab's cPanel server not available. so I can't test it now.
for reference:
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:reverse_proxy_cache
1. Create Web Server External App
Name:127.0.0.1
Address:127.0.0.1:80
for reference:
http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:reverse_proxy_cache
1. Create Web Server External App
Name:127.0.0.1
Address:127.0.0.1:80
No luck so far !
I tried creating a webserver with name 127.0.0.1:80 but it didn't change anything to I set the name to 127.0.0.1 and the address to 127.0.0.1:80 but now autoconfig.domain.tld times out after 60 seconds with a 403 error and nothing in the error_log file.
Even without this entry un the listeners list I see :
As I updated to litespeed 4.2.2 just after updating to cPanel 11.36 and having not tried to access autoconfig.domain.tld before (this feature was first introduced in 11.34) I don't know if the probem was added by LS 4.2.2 or if LS was never working with the autoconfig subdomain
I tried creating a webserver with name 127.0.0.1:80 but it didn't change anything to I set the name to 127.0.0.1 and the address to 127.0.0.1:80 but now autoconfig.domain.tld times out after 60 seconds with a 403 error and nothing in the error_log file.
Even without this entry un the listeners list I see :
As I updated to litespeed 4.2.2 just after updating to cPanel 11.36 and having not tried to access autoconfig.domain.tld before (this feature was first introduced in 11.34) I don't know if the probem was added by LS 4.2.2 or if LS was never working with the autoconfig subdomain
For proxy external app, it only handles http://127.0.0.1/ instead of alias like /sys-cgi/ which has to be defined as context in lsws (available at vhost level not server level). so this autoconfig and autodiscover which proxy through cgi-sys cgi is not working in lsws at the moment. will let you know once a fix is available.
