Really odd reverse proxy issues - Desktop vs Android

What is the problem?

Having an odd issue with binding octoprint behind a reverse proxy on two separate instances of octoprint behind the same dns name with paths and looking for a second set of eyes. It should be noted that I HAVE NO ISSUES AT ALL when navigating from a desktop version of brave/chrome/firefox. However, on android I cannot connect with chrome/firefox with the error "Loading failed" and to check the browser's console which I cannot do on android without USB debugging which I'm not in a good position to do.

The error suggests though that something is off with the X-Server-Name setting the baseURL path.

traefik config:

http:
  routers:
    octoprint:
      rule: "Host(`xxxxx.com`) && PathPrefix(`/e5`)"
      service: octoprint-service
      tls: {}
      entrypoints:
        - web
        - websecure
      middlewares:
        - default
        - authelia
        - e5header
        - e5strip
  services:
    octoprint-service:
      loadBalancer:
        servers:
          - url: http://xxxxxxxx

  middlewares:
    e5header:
      headers:
        customRequestHeaders:
          X-Script-Name: "/e5"  
          X-Scheme: "https" 

    e5strip:
      stripPrefix:
        prefixes:
          - "/e5" 

So the idea here is xxxxx.com/{a,b,c} to access that specific instance of octoprint.

Again, it's a weird one. It works perfectly fine when from desktop based chrome/brave/firefox, but not at all from android (any browser I tried). Even more weird is the fact that the headers are enforced at the reverse proxy to octoprint so to my knowledge the only issue that could be happening here is some script issue within octoprint not actually allowing or using the X-Script-Name/X-Scheme to configure the script to talk back to octoprint.

=== I will fully admit that while I've haxed together my fair share of python/go, I am no developer and would probably make a real developer feel pretty good about their work, so while I am willing to try anything or dig in, my actual understanding may be limited here. ===

What did you already try to solve it?

Beating my head against a wall trying to make chrome debugging actually work.

Have you tried running in safe mode?

yes

Did running in safe mode solve the problem?

no

Systeminfo Bundle

na, both instances are just default octoprint (with plugins). I have also tried a third stock instance with no plugins, as well as safe mode on all three.

Additional information about your setup

user --> Traefik <-- authelia --> octoprint

Update: To make this more confusing, I've just discovered that navigating to x.com/{a,b,c}/{#temp,#control,#gcode,#term,#timelapse} on android DOES in fact load the page without error :thinking:

Still no issues on desktop, loading the base URL redirects to #temp as expected.