Getting the error
Error : External Error - Linode DNS error [401] {"errors":[{"reason":"Invalid Token"}]}
Trying to uninstall this app.
Getting the error
Error : External Error - Linode DNS error [401] {"errors":[{"reason":"Invalid Token"}]}
Trying to uninstall this app.
But there is a new official fork at the following domain and it is slowly coming, but that is because they have to remove all of the copyright words like "phabricator" and "phacility" from everything.
@nebulon It is on Linode.
I'm not using Linode Firewall. I'm using ufw on the box.
No matter how I unblock this port, this error stays.
I have the following:
And only https://static.songer.pro works.
I restarted each app multiple times and I don't know what to do to get working again.
@girish Yeah I was able to get my.kloudscout.com up. But I get this alot.
yeah Ghost doesnt' want to start.
I can't reach my
● box.service - Cloudron Admin
Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-03-17 06:04:08 UTC; 1 weeks 1 days ago
Main PID: 17420 (node)
Tasks: 11 (limit: 2342)
CGroup: /system.slice/box.service
└─17420 node /home/yellowtent/box/box.js
Mar 25 23:30:29 ip-172-31-1-28 sudo[13488]: yellowtent : unable to resolve host ip-172-31-1-28
Mar 25 23:30:29 ip-172-31-1-28 sudo[13488]: pam_unix(sudo:session): session opened for user root
by (uid=0)
Mar 25 23:33:15 ip-172-31-1-28 sudo[13488]: pam_unix(sudo:session): session closed for user root
Mar 26 00:00:51 ip-172-31-1-28 sudo[13929]: yellowtent : unable to resolve host ip-172-31-1-28
Mar 26 00:00:51 ip-172-31-1-28 sudo[13929]: pam_unix(sudo:session): session opened for user root
by (uid=0)
Mar 26 00:03:17 ip-172-31-1-28 sudo[13929]: pam_unix(sudo:session): session closed for user root
Mar 26 01:30:40 ip-172-31-1-28 sudo[14717]: yellowtent : unable to resolve host ip-172-31-1-28
Mar 26 01:30:40 ip-172-31-1-28 sudo[14717]: pam_unix(sudo:session): session opened for user root
by (uid=0)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable
I perform this command /home/yellowtent/platformdata/logs/box.log
I'm unable to get to the site. https://my.kloudscout.com
2021-03-25T09:22:20.119Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:22:30.170Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:22:40.108Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:22:50.115Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:00.112Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:10.109Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:20.119Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:30.117Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:40.109Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:23:50.165Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:00.115Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:10.103Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:20.121Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:30.111Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:40.110Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:24:50.107Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:00.119Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:10.107Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:20.511Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:30.110Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:40.108Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:25:50.113Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:00.110Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:10.114Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:20.115Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:30.112Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:40.109Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:26:50.109Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:27:00.130Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:27:10.116Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:27:20.115Z box:apphealthmonitor app health: 6 alive / 1 dead.
2021-03-25T09:27:27.010Z box:updatechecker checkBoxUpdates: checking for updates
2021-03-25T09:27:27.555Z box:updatechecker checkBoxUpdates: no updates
2021-03-25T09:27:27.556Z box:updatechecker checkAppUpdates: checking for updates
2021-03-25T09:27:29.011Z box:updatechecker checkAppUpdates: Skipping app update notification of 6c8d88ba-7279-4141-947d-4aa0a4e3e45b since user was already notified of 1.47.0
My Blog https://songer.pro
Gives me this.
Mar 25 23:08:37 json: updated "/app/data/config.production.json" in-place
Mar 25 23:08:37 json: updated "/app/data/config.production.json" in-place
Mar 25 23:08:44 ==> Migrating database
Mar 25 23:08:44 ==> Loading /app/data/env for potential overrides
Mar 25 23:09:15 [2021-03-26 04:09:15] ERROR connect ECONNREFUSED 172.18.0.4:3306
Mar 25 23:09:15
Mar 25 23:09:15 connect ECONNREFUSED 172.18.0.4:3306
Mar 25 23:09:15
Mar 25 23:09:15 "Unknown database error"
Mar 25 23:09:15
Mar 25 23:09:15 Error ID:
Mar 25 23:09:15 500
Mar 25 23:09:15
Mar 25 23:09:15 Error Code:
Mar 25 23:09:15 DATABASE_CREATION_FAILED
Mar 25 23:09:15
Mar 25 23:09:15 ----------------------------------------
Mar 25 23:09:15
Mar 25 23:09:15 DatabaseError: connect ECONNREFUSED 172.18.0.4:3306
Mar 25 23:09:15 at DatabaseError.KnexMigrateError (/home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/errors.js:7:26)
Mar 25 23:09:15 at new DatabaseError (/home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/errors.js:55:26)
Mar 25 23:09:15 at /home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/database.js:128:19
Mar 25 23:09:15 at processTicksAndRejections (internal/process/task_queues.js:93:5)
Mar 25 23:09:15
Mar 25 23:09:15 DatabaseError: connect ECONNREFUSED 172.18.0.4:3306
Mar 25 23:09:15 at DatabaseError.KnexMigrateError (/home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/errors.js:7:26)
Mar 25 23:09:15 at new DatabaseError (/home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/errors.js:55:26)
Mar 25 23:09:15 at /home/cloudron/ghost/versions/4.0.1/node_modules/knex-migrator/lib/database.js:48:19
Mar 25 23:09:15 at processTicksAndRejections (internal/process/task_queues.js:93:5)
Mar 25 23:09:15
Mar 25 23:09:15 Error: connect ECONNREFUSED 172.18.0.4:3306
Mar 25 23:09:15 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
Mar 25 23:09:15 --------------------
Mar 25 23:09:15 at Protocol._enqueue (/home/cloudron/ghost/versions/4.0.1/node_modules/mysql/lib/protocol/Protocol.js:144:48)
Mar 25 23:09:15 at Protocol.handshake (/home/cloudron/ghost/versions/4.0.1/node_modules/mysql/lib/protocol/Protocol.js:51:23)
Mar 25 23:09:15 at Connection.connect (/home/cloudron/ghost/versions/4.0.1/node_modules/mysql/lib/Connection.js:116:18)
Mar 25 23:09:15 at /home/cloudron/ghost/versions/4.0.1/node_modules/knex/lib/dialects/mysql/index.js:68:18
Mar 25 23:09:15 at new Promise (<anonymous>)
Mar 25 23:09:15 at Client_MySQL.acquireRawConnection (/home/cloudron/ghost/versions/4.0.1/node_modules/knex/lib/dialects/mysql/index.js:63:12)
Mar 25 23:09:15 at create (/home/cloudron/ghost/versions/4.0.1/node_modules/knex/lib/client.js:290:39)
Mar 25 23:09:15 at processTicksAndRejections (internal/process/task_queues.js:93:5)
User tries to create an account for Mattermost and gets this
Received invalid response from the server
Well I'm using AWS and I need to upgrade the CPU and RAM. Is there a way of doing that in AWS without having to resize the disk?
Is there any steps I must do before resizing and upgrading the server that runs cloudron.
Yup. This makes no sense.
This section just continues to load until it timesout as well.
Should I try restart the server now? Just to see if that resolves it now.
@girish said in Try to go to App Store, but it just times out.:
host api.cloudron.io 8.8.8.8
It looks like creating a rule for outbound UDP 53 worked, but that's weird cause it was already setup for All ports outbound to be open.
ubuntu@ip-172-31-1-28:~$ host api.cloudron.io 8.8.8.8
Using domain server:
Name: 8.8.8.8
Address: 8.8.8.8#53
Aliases:
api.cloudron.io has address ##.#.##.###
ubuntu@ip-172-31-1-28:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
when I do this ping it just sticks there and doesn't complete.
There was a security update that happen on the dashboard and pretty much afterwards it stopped connecting to the Appstore. I'm going to create a outbound rule for UDP 53 to see if it forces it or something.
My outbound is completely open. I'm using AWS defaults. The only ports I have change is TCP ports related to the email.
@girish typo. .
Results
ubuntu@ip-172-31-1-28:~$ host api.cloudron.io
;; connection timed out; no servers could be reached
ubuntu@ip-172-31-1-28:~$ ^C
ubuntu@ip-172-31-1-28:~$ host api.cloudron.io 8.8.8.8
;; connection timed out; no servers could be reached
ubuntu@ip-172-31-1-28:~$ host api.cloudron.io 127.0.0.1
;; connection timed out; no servers could be reached
ubuntu@ip-172-31-1-28:~$ systemctl status unbound
● unbound.service - Unbound DNS Resolver
Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-08-12 21:04:49 UTC; 19h ago
Main PID: 859 (unbound)
Tasks: 1 (limit: 2342)
CGroup: /system.slice/unbound.service
└─859 /usr/sbin/unbound -d
Aug 12 21:04:49 ip-172-31-1-28 systemd[1]: Started Unbound DNS Resolver.
Aug 12 21:04:49 ip-172-31-1-28 unbound[859]: [859:0] notice: init module 0: subnet
Aug 12 21:04:49 ip-172-31-1-28 unbound[859]: [859:0] notice: init module 1: validator
Aug 12 21:04:49 ip-172-31-1-28 unbound[859]: [859:0] notice: init module 2: iterator
ubuntu@ip-172-31-1-28:~$ sudo systemctl restart unbound
sudo: unable to resolve host ip-172-31-1-28: Resource temporarily unavailable
ubuntu@ip-172-31-1-28:~$ host api.cloudtron.io
;; connection timed out; no servers could be reached
It just times out like this. I even restart the server. Nothing... This is ridiclous.
I'm guessing this has to do with it.
2020-08-13T01:38:29.201Z ERROR Error getting IP getaddrinfo EAI_AGAIN api.cloudron.io api.cloudron.io:443 [ /home/yellowtent/box/src/sysinfo/generic.js:22:25 ]
stack:
"""
Error: getaddrinfo EAI_AGAIN api.cloudron.io api.cloudron.io:443
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:56:26)
"""
message: getaddrinfo EAI_AGAIN api.cloudron.io api.cloudron.io:443
errno: EAI_AGAIN
code: EAI_AGAIN
syscall: getaddrinfo
hostname: api.cloudron.io
host: api.cloudron.io
port: 443