Connection problems

[jwqos]

What type of hardware are you using: Raspberry Pi 3, 4+
What YunoHost version are you running: 12.0.11
How are you able to access your server: The webadmin
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no

Describe your issue

I have my server on network A and connections in network A works as usuall, also on mobile 4g all connetions work, but then when I go to network B I can’t connect at all to my server, on network B I also have another yunohost server that is working fine everywhere. I suspect it’s some DNS problem, I have adguardhome installed in both servers and I see server A not being blocked on server’s B adguardhome. What could it be?

Share relevant logs or error messages

No idea what I could share, if you know please let me know and I will do it.

[ChriChri]

On your client in network B try ping <fqdn yunohost network A>. This should give you an IP even thought the ping might not work. Look at the IP:

• is it a private IP? Is it correct? Check routing and firewall between your client and the IP.
• is it the IP you use to access your host from the internet? Check that your NAT is configured correctly (hairpin nat).

[jwqos]

I have a static IP on both networks

@ChriChri

ping <fqdn yunohost network A>.

Could you please give an example of that command?

If it means simply “ping domain” or “ping ipaddress” of server A, I just did it from server B and it pings as expected, will try from my pc on network B later.

[jwqos]

I just did the ping from my PC on network B and it has some problems regarding IPv6, it’s unreachable. I don’t understand why IPv4 is not working though. On my server in network it works as expected, so it must be something blocking ipv4 on my clients in network B?

Not even SSH works

[ChriChri]

@jwqos

Could you please give an example of that command?

ping www.my-domain.org

[jwqos]

that’s what I thought, ping as usuall…thanks but I am not sure what to do, maybe disable ipv6 on server A?

[ChriChri]

Well, either you need to read up on all the more technical suggestions I made or you need to trust and reply with the result of the commands so that the network people here can get a better picture of what might be the problem and how to solve it.

Disabling IPv6 will probably not help. I’m guessing at a problem like this:

You resolve your fqdn (www.whatever-domain.org) and get the external IP in for your router. Then you try to connect to it, but you fail. You probably fail, because network address translation (nat) is only configured for the external interface of your router.

[jwqos]

How do I check if a yunohost server is blocking a certain IP address? Maybe that’s my case.

[jarod5001]

There are some topics on the forum having the same issue :

Can't update DynDNS

Solved: this turned out to be an issue with CryptPad: after uninstalling CryptPad I could successfully update my DynDNS

Bookworm migration problems, yunohost package fails to upgrade

I think I’ve solved this: I had an entry under /etc/yunohost/domains which had no default_app: set. That appears to be the NoneType in question: having populated that, regenerating works. I did check prior to this and yunohost domain info <mydomain> shows the app correctly, but it has to be in the file too. After that, upgrading the package works again. So I’ve re-ran sudo apt-get dist-upgrade and let that finish, which it has done successfully. After rebooting things were fine.

[SOLVED] DynDNS does not update after external IP changed, cannot force it either

Problem fixed, I had to delete my domain, and re-activate it to make the updates work for dyndns. get a .local domain move all apps to the .local domain make sure you have your domain recovery password, if not create a new one in the interface remove the domain and any of it’s sub-domains. 5.add a new domain with the same name as your old one (as I wanted to keep the name) 6.renew your let’s encrypt certificate enjoy your recovered access to your server. Good luck

DNS problems on one server after migration

Here’s what I did to fix the issue: get a .local domain move all apps to the .local domain make sure you have your domain recovery password, if not create a new one in the interface remove the domain and any of it’s sub-domains. 5.add a new domain with the same name as your old one (as I wanted to keep the name) 6.renew your let’s encrypt certificate enjoy your recovered access to your server. Good luck

[jwqos]

I just found out how to whitelist an IP address on fail2ban, that was the problem as I checked and found it on the logs being blocked. Problem solved!

[jarod5001]

Can you explain what you did so it may help others

[jwqos]

Sure, I had this insight about fail2ban, and in the logs there it was my LAN IP, then I simply edited this file: /etc/fail2ban/jail.conf whitelisting my IP in the line:

[DEFAULT]

ignoreip = 123.456.78.90