@nebulon Fantastic, thank you!

For completeness, the working instructions is: # cd /home/yellowtent/box # sudo -u yellowtent npm install aws-sdk@2.879.0 # systemctl restart box

@privsec That is what I personally call computer vodoo

@nebulon I find the solution taking infos from this forum . In fact, I opened port 53 TCP and UDP and Cloudron can resolve domain names. Configuration now is: [image: 1617633691304-firewall-template-resized.png] All seems to working fine... I marked this thread as "Solved"

@nebulon Yes, thank you. I found it!

@scooke Thank you. Good tip. I shall use this.

@msbt I tried a simple restore of my backup from my instance at DiscourseHosting and it worked flawlessly. The versions the same.

Thank you all ever so much for your effort. I was able to achieve all I need the way you suggested.

@odie Still stuck on this. The culprit is definitely that the usb network card fails to receive its configuration on boot. I cannot get netmanager to configure and initialize it at all. Only the two manual commands seem to work: sudo ip addr add 192.168.9.101/24 dev enxc4411eb4c476 sudo ip link set dev enxc4411eb4c476 up I have tried various thing with network manager, and I've tried adding a config file to systemd-networkd under /etc/systemd/network/ - the only thing I achieved, was to have every network freeze when I inserted the usb ethernet adapter (only to unfreeze as soon as I disconnected it). Tried keeping it disconnected for longer, just to see, but connections were frozen until I unplugged the usb network card. So I had to remove these config files. Can anyone offer suggestions? I don't know where to even look for assistance on this now... Thanks!

@d19dotca thanks for reporting. The 404s only come from map files for the minified 3rdparty libraries here. Those are only fetched if you open the webinspector to enabled nicer debugging, so those are non-fatal and can safely be ignored.

Thanks a lot guys, really appreciated for the input. Actually I am using vultr.com now, just made the upgrade of my server with it.

@austinsonger Not that you needed even more confirmations, but I can also confirm that all three links work fine from here in Canada.

@girish Awesome thank you, I appreciate the advice. All seems to be working great now. Also thanks @marcusquinn

@imc67 in the next release, we will suppress those notifications. it seems to not add much value. in any case, the solution is just to wait since cloudron will try again later. it's not a Cloudron issue, the LE service just goes up/down by nature.

@girish Thank's! Good the idea to end DST...

@d19dotca it's not a problem. Just the natue of any service being exposed to the internet. There a bots, misconfigured services, compromised iot devices doing all sorts of things. Nothing to worry.

Generally, I am wary of putting this information for general use (and even in docs) because many things can go wrong . So, please, if you care about the data, don't hesitate to contact us on support@ . We help regardless of the subscription plan.

@girish thanks a lot for your answer.i appreciate.

@humptydumpty haha! whoops - on it - great find!!!

@nebulon I enabled remote debugging and emailed, look forward to hearing back