Home Assistant App Ingress issue on latest release

[mmstano]

Hello,

referring to this issue on alexbelgium's repo. Upon updating to the latest release, users are getting 404 error's when trying to access netalertx using ingress. The dev had updated in January to accommodate changes, but apparently this new methodology isn't working with netalertx's latest release (v26.3.7+). The dev made this comment - alexbelgium/hassio-addons#2567 (comment)

My method to make ingress work in the previous version : I remove the BACKEND_API_URL which triggers an automatic usage of the ‘/server’ path that I dynamically convert to the ingress path using sub_filter in nginx. All those pieces of code are still there so the issue must be different however it goes so fast my browser debug mode cannot tell me which piece of code redirects to /device.php at the base url instead of using the subpath

There are no issues with the other app's that the dev offers on his repo and insists the issue is from a change in netalertx. Does anyone have any ideas on how to identify which piece of code redirects to /device.php at the base url?

[jokob-sk]

@mmstano regrettably I stopped using HASS in supervisor mode due to a recent migration to a new server, so I can't test this myself. Feel free to have a look at the code yourself - theoretically you should be able to debug on your own instance (you can edit files in teh NAX container)

In short BACKEND_API_URL is used only in 2 code files (the rest are translation documentation files): https://github.com/search?q=repo%3Anetalertx%2FNetAlertX+BACKEND_API_URL&type=code&p=1

The patch on alexs' side is probably either related to the

NetAlertX/front/js/api.js

Line 4 in 67cab9d

or

NetAlertX/front/php/server/util.php

Line 225 in 67cab9d

$apiBase = getSettingValue('BACKEND_API_URL') ?: 'http://localhost:20212';

files, but I could be wrong