Entering my nohost.me domain takes me to the router config page on my PC

Support
, ,
1

UPDATE: For anyone who comes across this in the future, the issue is that I do not have hairpinning set up in my router. Without that when the domain resolves, it resolves to the public IP of my router, and so every machine in the network thinks I want to talk to the router. Since my router does not support hairpinning I had to set the server as the DNS server for my router. It’s all explained in the YunoHost documentation: Get access back into YunoHost | Yunohost

What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.39 (stable)
How are you able to access your server: The webadmin
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: No

Describe your issue

I have Yunohost running on a small local PC with a nohost.me domain. However, whenever I enter <mydomain>.nohost.me into my web browser (both Firefox and Chromium) on my PC it takes me to the settings of my W-LAN rounter. Deleting browser data does not help. On my phone it works just fine, I get taken to the Yunohost login page. The server, the PC and the phone are in the same W-LAN network. When I manually enter the local IP address of my server I am taken to the Yunohost admin page. I can SSH into the server from my PC using ssh <user>@<ip-address>, but not ssh <user>@<mydomain>.nohost.me.

The fact that it affects only me PC suggests that there might be a configuration problem on the PC. I am running Void Linux. Here is my /etc/hosts file:

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>		<hostname.domain.org>	<hostname>
127.0.0.1		localhost.localdomain	localhost
::1			localhost.localdomain	localhost ip6-localhost

# End of file

I don’t know what other configuration to look for. Has anyone any ideas?

Share relevant logs or error messages

N/A

2

This is most likely a hairpinning issue, i.e. your router does not translate the public IP address of your domain to the local IP address of your server. It should however affect both your devices, this is surprising.

Your solution with the /etc/hosts file is the simplest one, you can check others on the linked page.

1 Like
3

Now all of the sudden it works. I had my phone hooked up to the PC for USB tethering because my W-LAN dongle sometimes gets unreliable (separate issue). After unplugging my phone and inserting the dongle once more the domain gets properly resolved.

How would I do that? Should I add an entry for each of my subdomains like this?

# 192.168.2.102 is the local IP of my server

192.168.2.102    <mydomain>.nohost.me    ???
192.168.2.102    photo.<mydomain>.nohost.me    ???
192.168.2.102    cloud.<mydomain>.nohost.me    ???

What should I enter at the <hostname>?

1 Like
4

That’s definitely weird :sweat_smile:

This should be enough.

5

It worked, thank you :slight_smile:

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.