https://documentation.cpanel.net/display/DD/WHM+API+1+Functions+-+unset_all_service_proxy_backends is probably the best solution but it removes all proxies. How do we check if other proxies are configured before we delete all of them?
Hello,
I just wanted to update that this is actually marked as resolved as of v90.0.08 and should no longer be causing an issue if you're on that version or higher. You can see this completion reflected in our changelogs here: 90 Change Log | cPanel & WHM Documentation
I just wanted to update that this is actually marked as resolved as of v90.0.08 and should no longer be causing an issue if you're on that version or higher. You can see this completion reflected in our changelogs here: 90 Change Log | cPanel & WHM Documentation
We're on v90.0.10 with 2 servers down today. Somehow the migrationtool has set a proxy to it self. Build scripts should be able to detect a loop and remove the wrong settings. (Even if they have been introduced prior to v90.0.08)
We've fixed the issues on our servers following this procedure (I think 
)
SSH to webserver (or terminal via WHM webinterface)
nano /var/cpanel/users/<account>
remove line PROXY_BACKEND=<webserver>
run script: /usr/local/cpanel/scripts/updateuserdomains
clear proxies via API: whmapi1 unset_all_service_proxy_backends username=<account>
run script: /scripts/rebuildhttpdconf
service httpd restart
What's missing for me is an API/script/interface to see what proxies are defined for an account (Or I don't know how to find them...)
So it was a bit of a gamble when removing all proxy backends.
The wrong proxy resulted in the following lines in /etc/apache2/conf/httpd.conf
<Location "/">
ProxyPass "http://<this webserver>"
ProxyPreserveHost on
</Location>
Scripts like /scripts/rebuildhttpdconf should see that ProxyPass is setting a proxy to itself, resulting in a loop followed by an unresponsive httpd.
I don't know if it's still benefitial to create a ticket....
)SSH to webserver (or terminal via WHM webinterface)
nano /var/cpanel/users/<account>
remove line PROXY_BACKEND=<webserver>
run script: /usr/local/cpanel/scripts/updateuserdomains
clear proxies via API: whmapi1 unset_all_service_proxy_backends username=<account>
run script: /scripts/rebuildhttpdconf
service httpd restart
What's missing for me is an API/script/interface to see what proxies are defined for an account (Or I don't know how to find them...)
So it was a bit of a gamble when removing all proxy backends.
The wrong proxy resulted in the following lines in /etc/apache2/conf/httpd.conf
<Location "/">
ProxyPass "http://<this webserver>"
ProxyPreserveHost on
</Location>
Scripts like /scripts/rebuildhttpdconf should see that ProxyPass is setting a proxy to itself, resulting in a loop followed by an unresponsive httpd.
I don't know if it's still benefitial to create a ticket....
SSL errors on htps://tickets.cpanel.net and first time logon shows way to much legal stuff. I'll file a ticket if the issues comes back.
@colo
What kind of SSL errors were you seeing? I wasn't able to replicate those when going to cPanel Customer Portal and if you run into the issue again, please do open a ticket so we can look into the issue further.
What kind of SSL errors were you seeing? I wasn't able to replicate those when going to cPanel Customer Portal and if you run into the issue again, please do open a ticket so we can look into the issue further.