Some applications are unable to get pinged - I am using a local domain in HTTPS
Title says most of it, i have a series of applications that Homarr is unable to ping, includes applications that doesnt require auth, like openspeedtest.
My setup looks like this: local.mydomain.yes, through NPM i have each app its sub domain. In Homarr, some apps are pinged correctly, some arent.
Solution:Jump to solution
i neglected the https:// in the domain given to homarr thinking it would automatically go https, instead, by default it was http
45 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
What error codes, if any, you get in the homarr logs?
how do i check homarr logs? docker container logs?
these are the logs
I'm guessing those responses may come from npm and not the app itself.
It's a bit strange that it shows the IP:port instead of your subdomain.domain.tld though, but that might be correct
If NPM is anything like traefik, it should provide you with local addresses that you can use when on the same network, which are less protected being in a close environment.
I gather you're already using it since you've mentioned using "local" in the address
what do you mean by less protected? HTTP over HTTPS?
all the connection refusals are happening at 192.168.2.1:80; is that the address of your NPM?
no, port 80 is not being used by anything
No, still https, just bypassing layers of authetication or filters like authelia.
Can you try pinging or tracerouting the affected services from your docker container?
It must be used by something, if that's where the blocking is happening. is that the address your domain forwards too?
No port 80 is just the default for http when resolving a domain to an ip. That's normal
But it should point to NPM which then points to the right service
@Alea Iacta Est can you double check the addresses in the JSON file proper?
I suspect a typo might cause a block at NPM
my local domain is pointing to that IP yes, 192.168.2.1 which is where i am hosting everything
and then through NPM i am re routing every app i have to a given subdomain, to their port
https://i.imgur.com/xK77ezm.png an example
where do i find the JSON
they are wherever you have mounted you homarr config folder.
im on it
what should i check?
if the domain is correct redirecting me to the app?
Exactly, sometimes some save errors can leave the internal url saved incorrectly after a typo; I've also had issues with trailing spaces in URLs before (why my mobile keyboard keeps adding trailing spaces I'll never know)
well it is
if i click on the app in homarr
it gets me to the app
Clicking the link sends you to the external URL.
Status checks are done against the internal URL.
Two different fields.
I use Traefik and have 0 issues with the status indicator for my Filebrowser.
However when you put a service behind a reverse proxy it usually can not be accessed by the LAN address. You have to go trough the proxy.
Therefore make sure you add the full domain name and NOT the local ip address to be monitored.
no, you guys didnt understand what is my setup
i have a local domain, pointing to my home network ip
the usage of the domain is only for SSL purpose, nothing else
pinging the local domain, pings my server ip, in this case is 192.168.2.1 just for info
local.domain.yes--->192.168.2.1
theres no external routing
Let's make it simple.
Go into your homarr's command shell and try to curl/wget the addresses that are not working.
See what those return as error (or not). This will at least make a baseline to tell us if your container can or cannot speak to those services
Make sure to triple check your addresses for typo, rewrite them completely by hand if necessary, just as a sanity check.
docker exec right?
Inside the homarr container
docker exec -it homarr
If your homarr's container ID is homarr then yes
But I'm not sure it is, so do
docker ps first to get the right idit is yeah
im installing curl in the container
i basically get the same exact error
connection refused
If you already have wget you can just use that instead
it returns my domain:80
This means that this problem isn't comming from homarr, but a problem in the setup.
yeah and that basically says its not a matter of "app auth" issue
might be NPM?
Can you try something for me?
Purposefully put in an incorrect subdomain to see if the error is the same or different.
yes
same error
ok guys
i am an idiot
Do you have the same settings inside NPM for the ones that work and the ones that don't?
like complete idiot
sorry for wasting your time
i got it fixed
Could you share the answer? As stupid as it may be, someone might come to have a similar issue and this would help them
oh it makes me very ashamed
well basically i run all my sub network in HTTPS/SSL
Solution
i neglected the https:// in the domain given to homarr thinking it would automatically go https, instead, by default it was http
and that explains everything
🙃
Well, I did say that port 80 was default for http, not https x)
If this makes it any better, it happens more often than you think.
It's the reason why we had to add a warning under the box about http/s.
should i ask a couple more questions? they arent related to this problem
You can do it in general if they are simple question or open a new ticket.
It makes it easier for others to search for relatable issues
got you