Cloudron Forum

When the domain is managed by a provider, say Google Cloud, I do not see this issue, I can add an A record from the DNS console, and I do this hybrid management. When I choose WildCard domain in the cloudron console, any A record I add to my DNS settings with my DNS provider, is not taking effect. It is like all subdomain access is hijacked with higher priority. And that was my original issue.

This was the basis of my original question.
https://i.imgur.com/3gtJVw1.png - wildcard means that all the *.thinnal.org will point to the cloudron's ip.
But interestingly, I have the root domain thinnal.org pointing to a different IP and it works fine.

I am following up here. @scooke

1. I added an A record to an IP against a domain managed by Cloudron - https://i.imgur.com/EXkfNKD.png
2. When I do nslookup, it points to the ip the cloudron is running - https://i.imgur.com/OatwR9K.png

---

@robi , @girish - with using app-proxy works. But I am running into a problem with Mixed content type as my nginx on the host is in http and I will have get certbot certs against the domain to serve against https.

I am hosting a family tree using a software called grampsweb and I want it host under a sub-domain that is managed by Cloudron.
In in google cloud console, I see that all the A record will be against the IP that cloudron is running and all sub-domains are effectively managed by cloudron, something like VHOSTS.

Now, if I want to host an application in a different instance(like grampsweb in a few digital ocean instance with an IP), and I want to point it to cloudron sub-domain, how can I go about doing this? I don't have a CNAME, I only have an IP address and I need to point it to an A record.

Thanks in advance.

Senthil

@archos

Thank you. That command helped. Now I have some broken images next to some profile pictures like using verified status pic (or something). I think, I check that next. But this was a huge help!

What is the possibility that some packages will need 3 days in 2 days? Do other administrators constantly upgrade their days every day or weekly?

I host my Mastodon on Cloudron, and due to the storage requirements, I do a regular clean up of old content.
Once I deleted the profile pictures and icons of the feeds by mistake, nad it has been showing up with broken icon pictures for me now.

I don't know how to fix it, I have tried a few ways to migrate, un-subscribe and re-subscribe. but doesn't help.
Any suggestions how to fix the icons that I have deleted from the static assets of the mastodon and make it recreate it again?

https://social.learntosolveit.com/home

The URL of the Broken link is like this

https://social.learntosolveit.com/system/cache/accounts/avatars/111/195/203/375/907/163/original/18170f36b1d0b6c6.jpeg

I must have deleted the cache folder in the system and I want to re-created. I thought, something called cache would be temporary store, but it seems it is not here.

Some of my Apps, like the Ghost App below shows Upgrade Required Constantly.

I have done 5 Updates since last two days and I visited the App Update log in the forum and didn't see as many updates.
What's happening here? Can I make sure cloudron can auto update the apps and not prompt me for upgrade all the time?

Hello, I am interesting running Teamcity Server in my cloudron instance.

The way to run the server using docker is given as

docker run --name teamcity-server-instance \
-v <path to data directory>:/data/teamcity_server/datadir \
-v <path to logs directory>:/opt/teamcity/logs \
-p <port on host>:8111 \
jetbrains/teamcity-server

How can I convert this into a "Cloudron" app? Can some point me the right direction or to a document / tutorial?
I have read how to the build cloudron app and looked the examples too, but I seem to missing

a) How to publish the app from a docker image directly?
b) Configure the volumes and the port as given here.

Thanks in advance.

Senthil

Could it be that ip address of the instance changed the service is not able to resolve to the new ip address?

The AWS LightSail IP-Address had changed, I had to manually go to my Google Cloud DNS, and update the ip-address to new ip-address and do a DNS Sync for other apps to update the ip-address.

I am bit surprised that DNS sync wasn't automatic when the host ip-address had changed. Am I missing anything?

I am using Cloudron on AWS LightSail. I rebooted my instance, stopped/ started. The services are coming up fine, but my dashboard is not loading.

My Dashboard URL : https://my.sourashtraassociation.org

Services

• Box

ubuntu@ip-172-26-4-82:~$ sudo systemctl status box
● box.service - Cloudron Admin
     Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-06-10 17:32:07 UTC; 7min ago
   Main PID: 1035 (node)
      Tasks: 11 (limit: 4710)
     Memory: 80.2M (max: 400.0M)
     CGroup: /system.slice/box.service
             └─1035 node /home/yellowtent/box/box.js

Jun 10 17:32:07 ip-172-26-4-82 systemd[1]: Started Cloudron Admin.
Jun 10 17:32:11 ip-172-26-4-82 sudo[1376]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 10 17:32:11 ip-172-26-4-82 sudo[1376]: pam_unix(sudo:session): session closed for user root
Jun 10 17:32:11 ip-172-26-4-82 sudo[1396]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 10 17:32:11 ip-172-26-4-82 sudo[1396]: pam_unix(sudo:session): session closed for user root
Jun 10 17:32:41 ip-172-26-4-82 sudo[3407]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 10 17:32:41 ip-172-26-4-82 sudo[3407]: pam_unix(sudo:session): session closed for user root
ubuntu@ip-172-26-4-82:~$ 

• Nginx

ubuntu@ip-172-26-4-82:~$ sudo systemctl status nginx
● nginx.service - nginx - high performance web server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/nginx.service.d
             └─cloudron.conf
     Active: active (running) since Sat 2023-06-10 17:32:05 UTC; 10min ago
       Docs: http://nginx.org/en/docs/
    Process: 742 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=0/SUCCESS)
   Main PID: 852 (nginx)
      Tasks: 3 (limit: 4710)
     Memory: 11.7M
     CGroup: /system.slice/nginx.service
             ├─ 852 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
             ├─3412 nginx: worker process
             └─3413 nginx: worker process

Jun 10 17:32:03 ip-172-26-4-82 systemd[1]: Starting nginx - high performance web server...
Jun 10 17:32:05 ip-172-26-4-82 systemd[1]: nginx.service: Can't open PID file /run/nginx.pid (yet?) after start: Operation not permitted
Jun 10 17:32:05 ip-172-26-4-82 systemd[1]: Started nginx - high performance web server.
ubuntu@ip-172-26-4-82:~$ 

• Unbound

ubuntu@ip-172-26-4-82:~$ sudo systemctl status unbound
● unbound.service - Unbound DNS Resolver
     Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2023-06-10 17:32:03 UTC; 10min ago
   Main PID: 670 (unbound)
      Tasks: 1 (limit: 4710)
     Memory: 9.6M
     CGroup: /system.slice/unbound.service
             └─670 /usr/sbin/unbound -d

Jun 10 17:32:03 ip-172-26-4-82 systemd[1]: Starting Unbound DNS Resolver...
Jun 10 17:32:03 ip-172-26-4-82 unbound[670]: [670:0] notice: init module 0: subnet
Jun 10 17:32:03 ip-172-26-4-82 unbound[670]: [670:0] notice: init module 1: validator
Jun 10 17:32:03 ip-172-26-4-82 unbound[670]: [670:0] notice: init module 2: iterator
Jun 10 17:32:03 ip-172-26-4-82 systemd[1]: Started Unbound DNS Resolver.
Jun 10 17:32:03 ip-172-26-4-82 unbound[670]: [670:0] info: start of service (unbound 1.9.4).
Jun 10 17:32:04 ip-172-26-4-82 unbound[670]: [670:0] info: generate keytag query _ta-4f66. NULL IN
Jun 10 17:37:13 ip-172-26-4-82 unbound[670]: [670:0] info: generate keytag query _ta-4f66. NULL IN

• Docker

ubuntu@ip-172-26-4-82:~$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/docker.service.d
             └─cloudron.conf
     Active: active (running) since Sat 2023-06-10 17:32:59 UTC; 10min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 873 (dockerd)
      Tasks: 50
     Memory: 140.7M
     CGroup: /system.slice/docker.service
             ├─ 873 /usr/bin/dockerd -H fd:// --log-driver=journald --exec-opt native.cgroupdriver=cgroupfs --storage-driver=overlay2 --experimental --ip6tables
             ├─1799 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 222 -container-ip 172.18.0.5 -container-port 22
             ├─1819 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 222 -container-ip fd00:c107:d509::8 -container-port 22
             └─2343 /usr/bin/docker-proxy -proto tcp -host-ip 127.0.0.1 -host-port 2003 -container-ip 172.18.0.6 -container-port 2003

Jun 10 17:40:00 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:40:00.463587881Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:40:07 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:40:07.284798767Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:40:56 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:40:56.855906990Z" level=info msg="ignoring event" container=1d27a105cae7bb27609489759ce4b8d9b333f0e591fe4>
Jun 10 17:41:01 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:41:01.053620336Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:42:20 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:42:20.688972713Z" level=info msg="ignoring event" container=252a4cd3c4a51a9f7c1ac13beb240286103d6395d9fdd>
Jun 10 17:42:21 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:42:21.621378971Z" level=info msg="ignoring event" container=85b87238bf6f44f11932cd849224487546baa866b43aa>
Jun 10 17:42:28 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:42:28.609166794Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:42:30 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:42:30.305650814Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:42:56 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:42:56.637321501Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>
Jun 10 17:43:13 ip-172-26-4-82 dockerd[873]: time="2023-06-10T17:43:13.689058221Z" level=info msg="ignoring event" container=7cc174cf515c225153365d18e42944a7e3f85c1757e6f>

• tail of the logs

tail -f /home/yellowtent/platformdata/logs/box.log
2023-06-10T17:43:50.020Z box:apphealthmonitor setHealth: 41b888a8-3bbe-4f98-bed0-88de0b07f97c (polltam.sourashtraassociation.org) waiting for 509.98 to update health
2023-06-10T17:43:51.067Z box:apphealthmonitor app health: 4 running / 3 stopped / 2 unresponsive

• Tail shows the apps are running.
• I am not sure why my dashboard and apps are not accessible.

Could it be that ip address of the instance changed the service is not able to resolve to the new ip address?

FWIW, I am using Google Cloud DNS.

Any troubleshooting suggestions?

Thank you,
Senthil

@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.

Thank you, @nebulon , @girish and @scooke .

@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.

---

• I am not sure why I had to change my resolved.conf for my DO instance.

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.

• I can login to other servers with my account, so it is not a minecraft issue.
• It has to be a server (host) or an app 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.