I can't open a case on this because I don't have enough details. Can someone assist me please?

When you access Plesk's SiteBuilder, the URL changes from 8443 SSL to uses port 8880 non-SSL.

When I add port 8880 as a local web service in the ASL WAF window, although I can open the SiteBuilder window and it initially looks like it will work, shortly after I get a message saying "SiteBuilder cannot access the sitebuilder server" and stops at that point.

Disabling the WAF on 8880 makes it work again.

I imagine the sitebuilder code is trying to do something that is being prevented by the redirection of port 8880. But the redirect is !127.0.0.1 so it should work unless .... errr... sitebuilder not being 127.0.0.1 ? Umm....

Faris.

so 8880 is the cleartext port right? Maybe its a http/https mixup?

I'm not quite sure what you are asking.

All I can say for sure is that although you login via https://domain-name.tld:8443, when you click on the Web Presence Builder link, a new page opens and there's some sort of redirection in action.

The address bar initially says https://domain-name.tld:8443/smb/something-or-other but then almost instantly changes to http://IP-ADDRESS:8880/sitebuilder/something-or-other

Note how we go from domain-name.tld to ip-address in the url (as well as going from https to http and 8443 to 8880).

At that point we get content in the page -- HTML, style and so on. We are not totally blocked. But whatever is running there can't communicate with "sitebuilder server" and throws an error.

The firewall redirect only affects non-localhost. And localhost has access to 8443 and 8880. So the redirect looks OK and not to blame? Maybe something that tortixd is (normally correctly) stopping from happening?

ah the smb thing, I think they're using @ in the url and in the context of a proxy in HTTP that means something else (its an authenticator token).