Same app not ping-able from different configs
I have a mobile config in addition to the default, but one app shows as pingable in the default config, but not in the mobile config.
NLooking at the downloaded config files, it looks like the working config has 2 entries for the app in question(?), where the mobile (broken) config only has one for the app
MAre the internal URLs of both apps exactly the same?
NSo maybe my config file was corrupted somehow?
NYes, the URLs are identical in all 3(!) entries: 2 in default, 1 in mobile
NI did see some application exceptions while editing text on a mobile device. Maybe corruption during/after crash?
Nnever mind, it looks like the URL appears in 2 entries in both files
NHmm, the name field in the broken file has different values for the two entries, where in the working file, the name field is identical in both entries
MCan you send the JSON of the apps here? Please remove any URLs or credentials that you don't want to post
Nsure, let me review the files..
Nuploaded (I think..)
mobile.json14.67KB
default.json40.67KB
NThe problematic entry is "kuma.svc.domain.com" in mobile, works in default
MIs any of the pings on mobile working?
MIf not the issue might lie in a wrong implementation for configs other than default:
No issue with your config, more one with our implementation. Will be fixed in the next release if so
const configName = getCookie('config-name'); is used in the ping function and then it tries to find the app id. If it of course uses the default configuration it will not be able to find it and so throw an NOT_FOUND error.No issue with your config, more one with our implementation. Will be fixed in the next release if so
NThanks. Please let me know if you need me write up an issue or something
NAnd pings work for all the other apps in the mobile config
MCan you check your server logs and share them here?
I guess there is an other issue
I guess there is an other issue
NHere are the docker logs:
homarr_logs.txt39.02KB
MThanks I'll check them tomorrow
MCan you maybe check if it works when you add the status code 401 to the ok status codes?
MIf it doesn't help you could also create a backup of your configurations and try if it works on dev.
T@nitin9641
NThe 401s in my log were for another app that required a username/password. I tried adding those to the unpingable app and it didn't work
Nis there a docker image for dev, or do I have to build from source?
NJust took a chance that
ghcr.io/ajnart/homarr:dev exists, and it appears toNAnd the bug is gone! Same configs, but now all the pings are gree
Nn
MNice. Please note, that dev will be less stable, @nitin9641
NMakes sense. If I want/need to switch back, I'l restore my configs from the :latest build first
MSure. Just always make sure, that you have a copy of your config as a backup, in case anything goes wrong.
MLet us know if you need any further help 
NThanks for the help!
MGreat!
