Broken LDAP, now no IPv4

Support
, ,
1

What type of hardware are you using: Raspberry Pi 3, 4+
What YunoHost version are you running: 12.1.12.1
How are you able to access your server: Direct access via physical keyboard/screen

Describe your issue

I woke up this morning unable to access the server via ssh nor web admin. I had the physically walk over and none of the users worked, only root. Swapping the localhost line from the slapd config got the service running but now I cannot get it to get an ipv4 address. It’s been running on a static dhcp lease (configured on router) and everything else in my network is getting addresses after flushing the router. I’m completely lost.

Share relevant logs or error messages

n/a

2

Hmmmokay but that seems unrelated to YunoHost itself like, YunoHost basically does not handle the network stack (except cases where you may have installed VPN/wireguard apps or similar) … Not sure what’s the relation with slapd exactly, maybe it was not happy that the system doesnt have an IPv4 idk

What if you just switch back to “regular” DHCP somehow ? (You can try forcing the system to get an IP from DHCP with dhclient <the interface name >

3

Maybe a firewall issue ?

Do you use vpnclient_ynh ?

4

Thanks for the replies guys. I don’t know what finally fixed the IP issue, but getting the IP back let me finally open the logs and see what went wrong: failed migration that I don’t remember running (I do have unattended-upgrades but got no e-mail about it).

It broke some apps too it seems–there’s no more nextcloud service listed even though the app is in the installed apps list. I’ll have to dig through everything later to see what’s actually still there.

I tried running the migration manually: [result].(https://paste.yunohost.org/raw/mopolocumo)

After the failure, if I try anything over ssh I’m met with sudo: you do not exist in the passwd database. Reading out the shadow file confirms that’s true. I then have to physically go to the server, open /etc/default/slapd, swap out the localhost:389 line for the one commented out right above it. Then I get my users back. Obviously, the migration is going to keep making that change.

I do have some edits to my hosts file, but I can ping localhost from the server no problem.

5

could you do

cat /etc/hosts
6 
0.0.0.0         localhost
127.0.0.1       localhost


127.0.1.1               yunohost

127.0.0.1       [[domain]]
127.0.0.1       onlyoffice.[[domain.tld]]
127.0.0.1 xmpp-upload.[[domain.tld]]
127.0.0.1 trilium.[[domain.tld]]
127.0.0.1 [[subdomain]].[[domain.tld]]
127.0.0.1 social.[[domain.tld]]
127.0.0.1 meet.[[domain.tld]]
127.0.0.1 stream.[[domain.tld]]
127.0.0.1 [[subdomain5]].[[domain.tld]]
127.0.0.1 [[subdomain2]].com
127.0.0.1 archive.[[domain.tld]]
127.0.0.1 podgrab.[[domain.tld]]
127.0.0.1 2fa.[[domain.tld]]
127.0.0.1 [[domain.tld]]
127.0.0.1 [[subdomain3]].[[domain.tld]]
127.0.0.1 sd.[[domain.tld]]
127.0.0.1 [[subdomain4]].[[domain.tld]]
127.0.0.1 printer.[[domain.tld]]
23.38.123.241 r3.o.lencr.org

I nuked the ipv6 stuff while I was troubleshooting this morning, could that be the problem? Most of the entries are from ~5 years ago before I had my DNS situation sorted. Even after fixing my DNS everything still worked so I never touched the hosts file again until today.

EDIT: every app wants to redirect to SSO now and all the SSO says is There is no app to list here, either because no web app yet is installed on the server, or because you don't have access to any. Please check with the admins of the server for more infos!

7

Yo dude wat teh frak is this line

It ain’t even Halloween season yet bro

What the aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

What the whyyyyyyyyyyyy

Like nonononononononon waaaaat

8

haha, if it was me, I could not tell you why. Again, haven’t touched this file in almost 5 years.

9

And it was working like that for 5 years? With no issues?

10

I assure you that is the case, hence my not questioning it. I figured my undertsanding of 0.0.0.0 meaning block MUST be wrong since yes, I was using it like this forever and I just pinged localhost and it worked like I said earlier.

My infrastructure was very different back then. Router with limited config, no DNS inside the network itself. Must have been something I copy/pasted to deal with double NAT maybe. I’m forcing all port 53 traffic to my DNs no matter what, maybe that’s what’s been obscuring the misconfig for so long?

11

This is exact thing is happening to me! Out of the blue too, things where working earlier this week and now all of sudden no apps are listed, but I do see them in the admin area.

(I do have unattended-upgrades but got no e-mail about it).

Coincidentally I’m also using unattended-upgrades.

Happy to start a new issue if that’s preferred too. :slightly_smiling_face:

12

Check your hosts file! If, like me, you don’t know what’s in there it’s the likely culprit.

13

Well, here it is. Although I have no idea how to determine if it’s correct (the way it’s supposed to be) or not… :thinking: :confounded_face: EDIT: Also, to the best of my knowledge, I have never manually edited this file and I’m positive I didn’t edit this file recently.

$ cat /etc/hosts

127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

xx.yy.z.z            portal.domain.tld

127.0.0.1       portal
14

Definitely not the same issue!

open /etc/default/slapd , swap out the localhost:389 line for the one commented out right above it.

Try that maybe. Think you need to restart the service too.

1 Like
15

Thanks for the suggestion! :heart_decoration:

I tried that but it doesn’t seem to do anything for my issue. :sob:

16

Just wanted to document that my issue was fixed with the latest YunoHost update (12.1.15.1).

17

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