• 3 Posts
Joined 1 year ago
Cake day: June 18th, 2023


  • Well yes but I am not sure that this is the main problem with flatpak containers.

    I’d rather point out that this approach creates a bigger attack surface since the containers tend to ship with outdated versions of libraries, frameworks and tools that the actual application relies on because it is now that specific app developer’s problem to update them inside of the container. So with this, even an up to date system is not really up to date and might suffer from severe vulnerabilities. I’d say it depends on your application, use case and threat scenario; containerization can make sense but is not the holy grail.

  • Not just Dell… bought an HP Elite x360 in 2018 and it had to go back twice too; first time because they jammed a physical blocker for non-LTE models into my sim slot (then sent it back after removing it and putting the same blocker back in, afterwards gave me free on-site repair for this issue, fucked up my board during that and came back next day with a replacement board) and second time because the keyboard died after a year. Solid ever since, still running perfectly but these initial issues should not happen with a 2500€ device.

  • Okay, then it simply has an issue with the addresses you are providing, as someone pointed out already, the issue likely is the 192.168.100 network. Find out where exactly you define localhost and as addresses to listen to and change them to e.g. and instead (or ideally just as this includes localhost as well). Restart the container afterwards, see if it works. Of course make a backup of your config first so you can go back.

  • Yes, have it running and it works well. Nextcloud setup is sth that I will still have to set up but the only problem I see there is certificates. To debug Nebula, simply try executing it by hand, e.g. nebula --config /path/config.yml and see what the error message is. Or check your journalctl of course. Share the message here and we can have a look!