17:43 <orzel> Hello

17:43 <orzel> (it seems the topic is outdated, my version is 9.0.2)

17:44 <orzel> The certificate for https://libreelec.wiki is invalid. Heard of let's encrypt ? :-)

17:55 <oblikoamorale> it is let's encrypt, just not renewed :)

17:56 <orzel> oblikoamorale: frequent renewing is part of it then !

17:57 <oblikoamorale> well so many things can go wrong :)

18:00 <orzel> I've changed my libreelec device for a brand new one. I've installed it from scratch. All i have to do is configure access to my NFS server. I remember it was straightforward. But it doesn't seem to be anymore. I haven't managed it yet

18:00 <orzel> If i go on 'nfs' and 'browse', it freezes, and then nothing happen. Not even an error message.

18:01 <orzel> i tried explicitely mentionning the server (name, or ip), but still nothing. Even adding the server ip + remote path doesn't work.

18:01 <orzel> It's all on ethernet, no wifi involved. All other computers and the previous libreelec install would connect to NFS without problem... i dont know where to look next

18:02 <orzel> i have ssh access to the le

18:04 <oblikoamorale> enable kodi debug logging and see if there's anything interesting in kodi.log

18:05 <oblikoamorale> (during failed browse / mount attempts)

18:33 <orzel> will try

18:36 <orzel> oh, actually there's already a log file. And it looks bad : https://pastebin.com/2LVstdcc

18:37 <orzel> As said , i tried both name and ip. Name resolution seems to fail, but this is weird, because when connected by ssh, i can ping <name>, without problem

18:38 <oblikoamorale> as a possible workaround you can try mounting your shares in systemd boot units and don't bother with kodi way

19:20 <orzel> yes, i saw the wiki page about this

19:38 <orzel> Ok, i still dont get it. Those log confirm there is a problem ("error getting nfs://"), but nothing more

19:39 <orzel> the network seems ok, i can browse/install extension, i can even see some upnp media server (though only few movies are there, i dont know why).

19:39 <orzel> but nfs doesn't work

19:39 <orzel> I installed this instance a few hours ago :-(

19:40 <orzel> Some pages mention adding 'insecure' to the nfs export. I never used that, it looks bad, and my previous le didn't need it

20:12 <orzel> tried it nevertheless, doesn't help

20:16 <orzel> i keep on getting weird dns error all in the log. While every request i try from ssh/cli does work, and /etc/resolv.conf seems perfect

20:16 <orzel> i even tried those domain names in the error message, and they do resolv