anubis breaks ajax / XHR, why? and how to fix?

[jamosdev]

I have apache on fedora 42 with let's encrypt, port 80 -> 443, port 443-> proxy pass to anubis (install via dnf -y install anubis) on port 8923, anubis is told to redirect to port 3000, apache also listens on port 3000 and the joomla php-fpm's website conf that was originally on 80/443 is on port 3000

if I open fedora firewall up to allow remote access to port 3000, and hit http://mysite.com:3000 then I can install joomla, and the ajax dashboard items in the admin panel work

but if I access https://mysite.com then all of those are failing due to xhr / ajax being blocked

firefox just says mixed block and a red circle with a line through it for the status

I have even set

 14         Header add Access-Control-Allow-Origin "*"
 15         Header add Access-Control-Allow-Headers "origin, x-requested-with, content-type"
 16         Header add Access-Control-Allow-Methods "PUT, GET, POST, DELETE, OPTIONS"
 17         Header always set Referrer-Policy "unsafe-url"

in the sites .conf file (the VirtualHost *:3000 one) to see if any of that will make it stop complaining / blocking XHR but nope, still problems

how can I make ajax work? and why is there any difference at all between the user putting an address in the URL bar and the loaded page requesting the same address via javascript?

If I remove anubis from the equation it all works normally, and if I open firewall to port 3000 and access http://mysite.com:3000 directly in the browser it all works normally as well

[jamosdev]

if you guys have any memory or tips or any knowledge of where to look further on this that would be helpful

[avioletheart]

seems like joomla thinks the connection is plaintext http, and telling the frontend to request things in plaintext instead of https.

i run wordpress and need this at the top of my wp-config.php, maybe joomla has something similar:

if (isset($_SERVER["HTTP_X_FORWARDED_PROTO"] ) && "https" == $_SERVER["HTTP_X_FORWARDED_PROTO"] ) {
$_SERVER["HTTPS"] = "on";
}

[jamosdev]

ah okay, yeah maybe its confused by the live_site being https:// but after anubis proxy it is seeing itself as http://

tho, I run another on my NAS which uses some kind of HTTPS->HTTP proxy pass thing (Synology Webstation) with a similar setup but maybe they do something smart

I'll try forcing joomla on the server to give https even if forwarded http somehow

[jamosdev]

yeah that's it.

For anyone doing a google search:

use :3000 (or whatever the direct port is, open the firewall if necessary) to generate the installed configuration.php else the installer won't work.

But once it's installed you can close that firewall again, and modify the installed configuration.php manually (you can't use the joomla admin web UI as it has a sanity test that will fail)

if you force ssl, it will infinite redirect as force_ssl just does a "if it is http, 304 them to https" in php, which is already being done by default let's encrypt on apache, and then it goes to anubis, and then it goes to http to joomla
$force_ssl = 0;
and then to make the ajax request URLS be https and not http, just set this:

$live_site = 'https://yoursitehere.com';

once these 2 are in place, it will work smoothly behind anubis in a default setup!

[jamosdev]

just forgot to add, it is important to forward some stuff on the proxy pass, else you still get infinite redirects on main site

   RequestHeader set "X-Real-Ip" expr=%{REMOTE_ADDR}
    RequestHeader set X-Forwarded-Proto "https"
    RequestHeader set "X-Http-Version" "%{SERVER_PROTOCOL}s"
    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:8923/
    ProxyPassReverse / http://127.0.0.1:8923/