Can't get Apache to reverse proxy to Jellyfin

[roomtin]

Hello. I'm trying to get apache2 on debian to be a reverse proxy so that I can connect to jellyfin remotely over https. The problem I'm encountering is that instead of loading jellyfin when I visit my https domain, I get the root apache2 directory that has a few other things in it I'm hosting. I can visit jellyfin locally through the web client using the internal IP of my home server just fine. I followed the apache2 guide here and replaced only the DOMAIN-NAME and SERVER-IP-ADDRESS instances with the correct information. One difference though is that I'm using a subdomain (e.g. media.mycoolserver.com) because I'm hosting other things at my domain, so I've included that full subdomain+domain in the places that asked for the DOMAIN-NAME, but I didn't think it would cause any difference.

I did also need to create the /var/www/html/jellyfin/public_html directory and give apache access to it, but there's nothing in it.

I've run sudo a2ensite for my .conf file in sites-available, and installed all the apache2 addons the jellyfin guide suggests.

systemd doesn't show any errors after reloading apahche2.

I've correctly set up a cert for my subdomain and it's at the location the jellyfin apache2 guide expects.

My uname -a:  Linux brrbox 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 2021-07-18 x86_64 GNU/Linux

I'm unsure where to look next or what information might be relevant to solve the problem and would appreciate any suggestions. Please advise what other information I should share. Thanks.

[TheDreadPirate]

Can you share your apache config via pastebin? Censor the domain name.

[roomtin]

Thanks for your reply. I was actually able to sort the issue myself. The problem was that I had some default apache2 configurations I never deleted that weren't being used, but were overriding something in my jellyfin config. If anyone else has this particular problem, you should check if you have VirtualHosts defined somewhere else in your apache2 configs that conflict or override your jellyfin one. Apache loads configurations in alphabetical order too, so that could cause some unintuitive behavior.