@christiaan said in Free cloud computing hosting:
A real free tier.
I doubt it. Perhaps you can you can use your home computer for hosting. That one time cost and minor addition to your shared electricity and internet bill.
@christiaan said in Free cloud computing hosting:
A real free tier.
I doubt it. Perhaps you can you can use your home computer for hosting. That one time cost and minor addition to your shared electricity and internet bill.
There is mismatch between package version and server version in the minecraft app.
Please see the screenshot.
Package version says 1.19.3
The internal server version is 1.19.2
@nebulon said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
oh this might then actually be an unbound issue.
Indeed, it was. Problem resolved.
@nebulon said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
oh this might then actually be an unbound issue.
Indeed, it was. Problem resolved.
@girish said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
Which Cloudron version are you on (atleast version 7.1 is needed). I don't think this is the problem, though.
For some reason, my digital ocean instance wasn't having a correct resolv.conf and I had to update it.
I was able to get the latest app version.
But I am still facing this problem with authentication error.
root@my:~# cat /etc/systemd/resolved.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details
[Resolve]
DNS=1.1.1.1 8.8.8.8
FallbackDNS=8.8.4.4
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
#DNSStubListener=yes
@girish said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
I pushed a new package yesterday 1.7.3-1 that fixes this. Can you check?
I don't see it. I tried check for updates and still shows 1.7.3
There is mismatch between package version and server version in the minecraft app.
Please see the screenshot.
Package version says 1.19.3
The internal server version is 1.19.2
I tried increasing the memory for the app, and still faced this issue.
If my system time is incorrect, would it affect only minecraft app? Is the system time in the docker container (cloudron app) or my digital ocean instance? Any thoughts / suggestions on this?
@nebulon said in Authentication Servers are Down. Please try again later, sorry! - Error message with Minecraft App 1.9.2:
Is this happening for a long time or related to mojangs auth servers? Please note that the user accounts within minecraft are actually minecraft accounts, not Cloudron accounts.
I am tried login to my server (cloudron minecraft app) after a while and I am seeing this.
Internet says it might be something do with server setup and not really an auth issue.
My minecraft service is running fine. But the application is throwing this error message.
I checked the logs and the error message was this
Jan 02 23:23:07 [07:23:07] [User Authenticator #1/INFO]: Disconnecting com.mojang.authlib.GameProfile@21e04568[id=<null>,name=multiverse1107,properties={},legacy=false] (/73.223.149.123:57121): Authentication servers are down. Please try again later, sorry!
Jan 02 23:23:07 [07:23:07] [User Authenticator #1/ERROR]: Couldn't verify username because servers are unavailable
Jan 02 23:23:07 [07:23:07] [Server thread/INFO]: com.mojang.authlib.GameProfile@21e04568[id=<null>,name=multiverse1107,properties={},legacy=false] (/73.223.149.123:57121) lost connection: Authentication servers are down. Please try again later, sorry!
I tried to reload and I got the warning.
Jan 02 23:30:05 [07:30:05] [Server thread/WARN]: Can't keep up! Is the server overloaded? Running 4964ms or 99 ticks behind
Any suggestions what is really happening?
@nebulon - Thank you.
Can I look forward to the Discourse 2.9.0 update. It will help me with a migration.
Thanks in advance.
@nebulon said in Google Sign In for Surfer:
so you could write small shell scripts for each site to avoid the risk of uploading to the wrong instance.
Yes, I do the same. Thank you.
@nebulon said in Google Sign In for Surfer:
The aim for Surfer is to be a quite slim static asset server. The current auth which is there was just trivial to add, since there was already the user-interface which was Cloudron auth enabled.
Thank you for this explanation.
I enjoy using it, and it filled in my need for static sites. I previously I used Github pages or Neltify.
Both had limitations and extra management that I avoid with surfer.
A different topic, but one feedback I had with surfer design was, I had to adop token based upload, with managing multiple sites from a single local computer. The global credential was security risk, when one of my site was private.