Custom Default Password.

Many N8N programs install using default usernames and passwords as opposed to active directory. Which is understandable.... however very insecure. If you forget to change that default password you could easily get crawled and hacked.

Solution

Create a global variable inside of Cloudron where an admin can customize the default username and passowrd for this type of application.

Example

Wordpress installs with the username admin, and password changeme
how awesome would it be if the changeme part was customized to "customdefaultpassword"

I have made some progress here apparently calcom needs access to a database while running yarn build, and while running yarn it would be writing to /app/code

So I created a temporary database so long as you build this on a server with access to postgres this will work. The only problem is that I cannot figure out why it is stuck on localhost:3000 as opposed to accepting the new dns settings

https://git.draglabs.com/davidjstrom/cloudron-calcom-v2/-/tree/localhost-issue

@girish
Any thoughts?

@subven

wordwrap!!! the problem was staring me in the face! But I could not see it because i did not scroll to the right...

Thanks for the help!!!!

I took a cert and key file from another server, and renamed the default cert to be whatever the error wanted.
first thedomain.com.cert, then thedomain.com.key. and so-forth until it loaded. It is working now! .

@girish

At the end of the day, I found the culpret.
Also upgraded to a bigger server.

While yes N8N will happily crash it's self - I had a few perfmance bottlenecks and for now N8N seems to be happy with the traffic. Here is a breakdown of the solution without setting up queue mode.

1. N8N uses postgress - so bumping up the RAM for N8N is not enough that just grows the list of RAM eating active processes, you also have to go bump the RAM for Postgres
2. I am using Baserow for logging and followup task Queueing. By default baserow only has 3 Auth workers which is not enough to cover heavy load. So I had to install the CLI and run the command cloudron env set --app baserow.draglabs.com BASEROW_AMOUNT_OF_GUNICORN_WORKERS=9

Conclusion - Step 1 Significantly improved the performance of N8N dropping normal RAM consumption by about 30%
Step 2 Caused active processes to complete 10X faster further reducing N8N footprint.

Now that I upgraded to 24 gigs I am only using 8

@robi

Related Feature Request. https://forum.cloudron.io/topic/7472/remote-file-access/5

It would be really awesome if rclone was implemented through the CLI enabling the synchronization of target directories and mounts.

In my specific use case I am trying to figure out a reliable way to be able to quickly edit my GRAV site. While GRAV has a GUI it was really build for the text editor.

I am trying right now to figure out how to install Rclone as a system level app to provide synchronization to my desktop computer of several cloudron folders.

If rclone was implemented in such a way that it could have access to other application's data folders that would be super awesome!

@girish said in out of space error leading to missing certs:

e-generate the nginx config for the dashboard alone. Once you have access to the dashboard, you can go to Location section of each app and click save. This will regenerate nginx config of the app

FIXED!!!

It is difficult to tell if deleting the conf files from the folder /etc/nginx/application and then restarting unbound Instructions then using systemctl restart nginx and systemctl restart box

I say that because unbound definitely was not working at at one point.
And as I remember nginx did start momentarily.

However the solution came when I deleted the corrupted zero byte private key from the folder /home/yellowtent/platformdata/nginx/cert/

When that file was deleted I was able to log in without ssl using firefox. Once in under the domains and certs section of cloudron I was able to click on Renew All Certs. That fixed SSL, and I was able to go into each program and re assign the dns settings by clicking save.

@mabaker @chetbaker I am working on this happy to join up and hack together on it. If you wanna hack on this with me just set a time on my calendar and we can work on it. https://short.draglabs.com/cal

I am running into this problem with N8N under heavy load it will easily take down Cloudron. On the N8N website they talk about "queue mode" where one instance of N8N drives another.

It is important to have n8n using postgres or mysql
And it is important to have redis running to direct the sub instances.

beyond that... I am wondering if it is going to be possible to make this happen while using Cloudron.

I have the current problem where a load spike will bring in 2000 requests in a few minutes which reliably crashes N8N. It seems premature to upgrade the whole server just to handle a load spike.

https://docs.n8n.io/hosting/scaling/queue-mode/

Any ideas?

@msbt
Hi, I would like to take a look at this. I recently built my own N8N instance. And would really like to get cal.com running on cloudron.

Could you share more of your work in progress?

I am interested in being able to override the source code in running apps for a number of reasons.

Reason 1. I Found a bug in N8N and need to test the code edit before I submit a PR. Maybe it is just a one line change but the ability to slip in a custom hot fix would be super awesome!

Reason 2. Also an N8N example, but hard customizations may be good for me but won't necessarily get approved. You know.. changing the way an API works etc. How awesome would it be to have some granular control over the code running on your server?

Idea... Would it be possible to overwrite the source location to my own github fork? Then I would be manually pulling in new updates as opposed to relying on whatever the community publishes.

Most Awesome... would be to have an override folder where I could re-define a specific page while maintaining the normal update system in the background.

I have been thinking about controlling some resources by running Cloudron within a docker instance. Any thought.

Docker within docker?

@girish
Which DNS provider you are using?

1. I am using cloudflare, but I have also had this issue with route53
   Is email enabled.
2. Yes, my primary inboxes are google inboxes, but I have configured gmail to use cloudron as a catch-all email server using routing rules.
3. On the subject of controls... I can also imagine situations where I would want to use a load balancer, or hosted spf service which again will trick Cloudron into thinking everything is set up wrong.

@nebulon
Dynamic DNS is not enabled.
And yes there is manual intervention I could click "update dns settings" I am a little OCD and get frustrated staring at red dots because I have a custom configuration here and there.

And just wish there was a way to tell cloudron "hey I know you think this record is wrong, but trust me its right and good" Or tell cloudron, "hey you can update A records and txt records but MX records those are off limits" or maybe a custom config file similar to a local hosts file where we could go in and take a record relationship and just straight up override it. This would enable configurations with load balancers, email routers, and hosted dmark utilities.

Normally I just set the DNS settings of Cloudron to manual, but I wish I did not have to do that. Especially because it always think I am wrong.

@jdaviescoates
I can confirm that yesterday and many times before it wiped out my gmail mx records which is especially frustrating because I have cloudron mx records configured in google admin.

Also, more reasonably it will overwrite an A record all day long.

In addition to that I have seen it overwrite my Dmarc policy which can be kinda annoying if you have dmarc records hosted through a tool like mx toolbox...

That is for both S3 and Cloudflare

Reoccuring problem with the automatic DNS features on Cloudron is that they will overwrite my MX records... so on one hand, it is really convenient that Cloudron can provision an A record, and it is really inconvenient that one click on the wrong button and it will overwrite my mx records.

It would be amazing if I could set restrictions allowing cloudron to write only A records and TXT records, leaving the MX for me to manage manually.

@roofboard Strangely when I set my hosts file to include the line

123.myserver.123.123 domain.com

it starts working and is all happy all of the sudden

NOTE one factor that my confuse matters is that I recently switched to cloudflare so the exact issue which started this thread may not be causing dns issue.

Also... after logging into cloudflare and disabling proxy service it seems to be working.

Question... Is there any issues with Cloudflare proxy?

@subven
Did a few things...

1. When I came back to the problem today cloudron was down again, this time with too many redirects on all services.
   So... I tried upgrading ubuntu, following this guide. https://docs.cloudron.io/guides/upgrade-ubuntu-22/
   When I finished the step "apt upgrade" and rebooted the server it started working again. GREAT!!

But... still I moving to a new server sounds like a good idea.
Moving to a new server, 301 redirect issue

So I started with conabo VPS they seem to be a great deal.
I provisioned a 16gb Ram, 200gb machine and installed ubuntu 22
.

After following these instructions to migrate the server from backup
https://docs.cloudron.io/backups/#restore-cloudron

The new server is almost working.

Now, I am having the old problem of too many redirects. All of my services seem to have an infinite loop of 301 redirects pointing to the same location.

history of the too many redirects problem
I have been getting tired of route53 and have an interest in the security features built into cloudflare. So after getting things up an running yesterday I made the switch over to cloudflare. After making that switch I started getting a 301 redirect loop (still on the old server)

After running the apt update / upgrade the problem resolved.

So I figured that I was good to go for moving over to the new VPS.

@nebulon
this problem has been ongoing for a number of weeks server goes down and scheduling a downdetector to restart Cloudron every time it crashes seems.... lame.

I think this is the 10th time, just first time I did a good job collecting logs and taking screenshots.

@nebulon here are the logs leading up to rebooting the server - Note when i restarted box it helped only temporarily but when i reboot the server i get much more uptime.

there are some time gaps because i had to truncate out noise to get under the char limit

2022-12-15T16:15:40.145Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:15:50.034Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 369.967 to update health
2022-12-15T16:15:50.170Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:16:00.051Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 359.95 to update health
2022-12-15T16:16:00.231Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:16:10.052Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 349.949 to update health
2022-12-15T16:16:10.209Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:16:11.595Z box:shell statusUnbound exec: systemctl is-active unbound
2022-12-15T16:16:11.615Z box:shell statusUnbound (stdout): active

2022-12-15T16:16:11.615Z box:shell statusUnbound (stderr): null
2022-12-15T16:16:11.668Z box:shell statusNginx exec: systemctl is-active nginx
2022-12-15T16:16:11.689Z box:shell statusNginx (stdout): active

2022-12-15T16:16:11.689Z box:shell statusNginx (stderr): null
2022-12-15T16:16:20.025Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 339.976 to update health
2022-12-15T16:16:20.155Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:16:20.674Z box:cloudron Getting logs for box as json
2022-12-15T16:16:30.036Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 329.965 to update health
2022-12-15T16:20:20.152Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:20:30.037Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 89.964 to update health
2022-12-15T16:20:30.194Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:20:40.040Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 79.963 to update health
2022-12-15T16:20:40.136Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:20:50.037Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 69.964 to update health
2022-12-15T16:20:50.164Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:00.048Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 59.953 to update health
2022-12-15T16:21:00.196Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:10.460Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 49.541 to update health
2022-12-15T16:21:10.460Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:20.045Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 39.956 to update health
2022-12-15T16:21:20.211Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:30.036Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 29.965 to update health
2022-12-15T16:21:30.178Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:40.039Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 19.962 to update health
2022-12-15T16:21:40.179Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:21:50.031Z box:apphealthmonitor setHealth: f30ffad7-b996-4ecc-a6cf-c375ab916f19 (help.troubled-nodebb-installation.com) waiting for 9.97 to update health
2022-12-15T16:21:50.202Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:22:00.175Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:22:10.175Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:22:20.175Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:29:30.233Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:29:40.147Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:29:50.245Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:00.007Z box:disks checkDiskSpace: checking disk space
2022-12-15T16:30:00.059Z box:janitor Cleaning up expired tokens
2022-12-15T16:30:00.065Z box:janitor Cleaned up 0 expired tokens
2022-12-15T16:30:00.432Z box:disks checkDiskSpace: disk space checked. out of space: no
2022-12-15T16:30:00.450Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:10.402Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:20.150Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:30.170Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:40.184Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:30:50.194Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:31:00.163Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:31:10.185Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T16:31:20.140Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:32:40.168Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:32:50.121Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:00.191Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:10.171Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:21.168Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:30.173Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:40.164Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:33:50.164Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:00.232Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:10.194Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:20.199Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:30.163Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:40.142Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:34:50.194Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:00.211Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:10.115Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:20.176Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:30.167Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:41.721Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:35:50.166Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:00.155Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:10.201Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:20.220Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:30.175Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:40.187Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:36:50.222Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:00.148Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:10.219Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:20.148Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:30.151Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:40.217Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:37:50.184Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:00.127Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:10.180Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:20.131Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:30.158Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:40.128Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:38:50.155Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:00.214Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:10.203Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:20.135Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:30.184Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:40.206Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:39:50.159Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:00.203Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:10.169Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:20.129Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:30.214Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:40.165Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:40:50.147Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:00.182Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:10.193Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:21.093Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:30.212Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:40.137Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:50.202Z box:apphealthmonitor app health: 15 running / 2 stopped / 1 unresponsive
2022-12-15T17:41:55.205Z box:box Received SIGTERM. Shutting down.
2022-12-15T17:41:55.207Z box:tasks stopAllTasks: stopping all tasks
2022-12-15T17:41:55.208Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-12-15T17:41:58.578Z box:cloudron Getting logs for box as json
2022-12-15T17:43:00.113Z box:server ==========================================
2022-12-15T17:43:00.127Z box:server            Cloudron 7.3.4  
2022-12-15T17:43:00.127Z box:server ==========================================
2022-12-15T17:43:00.573Z box:settings initCache: pre-load settings
2022-12-15T17:43:00.635Z box:tasks stopAllTasks: stopping all tasks
2022-12-15T17:43:00.636Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
2022-12-15T17:43:00.925Z box:shell stopTask (stdout): All tasks stopped

From time to time cloudron crashes.

All services stop working, and when the my.domain.com finally loads it looks just like this.

and when I log into cloudron I can 'fix' it by restarting box, then everything goes back to normal.

root@my:~# 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 Fri 2022-11-18 02:01:06 UTC; 3 weeks 6 days ago
       Docs: http://nginx.org/en/docs/
   Main PID: 5728 (nginx)
      Tasks: 7 (limit: 28752)
     Memory: 46.8M
     CGroup: /system.slice/nginx.service
             ├─  5728 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf
             ├─424780 nginx: worker process
             ├─424781 nginx: worker process
             ├─424782 nginx: worker process
             ├─424783 nginx: worker process
             ├─424784 nginx: worker process
             └─424785 nginx: worker process

Warning: journal has been rotated since unit was started, output may be incomplete.
root@my:~# systemctl status box
● box.service - Cloudron Admin
     Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-12-05 09:14:04 UTC; 1 weeks 3 days ago
    Process: 501731 ExecReload=/usr/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
   Main PID: 3006796 (node)
      Tasks: 11 (limit: 28752)
     Memory: 100.8M (max: 400.0M)
     CGroup: /system.slice/box.service
             └─3006796 node /home/yellowtent/box/box.js

Dec 15 03:23:00 my.domain.com sudo[691844]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 03:24:05 my.domain.com sudo[691844]: pam_unix(sudo:session): session closed for user root
Dec 15 03:30:00 my.domain.com sudo[696164]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 03:34:23 my.domain.com sudo[696164]: pam_unix(sudo:session): session closed for user root
Dec 15 05:30:00 my.domain.com sudo[768909]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 05:35:34 my.domain.com sudo[768909]: pam_unix(sudo:session): session closed for user root
Dec 15 07:00:05 my.domain.com sudo[823705]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 07:04:32 my.domain.com sudo[823705]: pam_unix(sudo:session): session closed for user root
Warning: journal has been rotated since unit was started, output may be incomplete.
root@my:~# systemctl status unbound
● unbound.service - Unbound DNS Resolver
     Loaded: loaded (/etc/systemd/system/unbound.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-12-05 09:14:03 UTC; 1 weeks 3 days ago
   Main PID: 3006652 (unbound)
      Tasks: 1 (limit: 28752)
     Memory: 21.8M
     CGroup: /system.slice/unbound.service
             └─3006652 /usr/sbin/unbound -d

Dec 15 15:07:41 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:12:52 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:18:01 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:23:12 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:28:27 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:33:39 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:38:52 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:44:05 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:49:17 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
Dec 15 15:54:30 my.domain.com unbound[3006652]: [3006652:0] info: generate keytag query _ta-4f66. NULL IN
root@my:~# systemctl restart box
root@my:~# systemctl status box
● box.service - Cloudron Admin
     Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2022-12-15 16:01:45 UTC; 10min ago
   Main PID: 1152712 (node)
      Tasks: 11 (limit: 28752)
     Memory: 82.9M (max: 400.0M)
     CGroup: /system.slice/box.service
             └─1152712 node /home/yellowtent/box/box.js

Dec 15 16:01:45 my.domain.com systemd[1]: Started Cloudron Admin.
Dec 15 16:01:47 my.domain.com sudo[1152769]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 16:01:47 my.domain.com sudo[1152769]: pam_unix(sudo:session): session closed for user root
Dec 15 16:01:47 my.domain.com sudo[1152777]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 16:01:57 my.domain.com sudo[1152777]: pam_unix(sudo:session): session closed for user root
Dec 15 16:02:27 my.domain.com sudo[1153127]: pam_unix(sudo:session): session opened for user root by (uid=0)
Dec 15 16:02:53 my.domain.com sudo[1153127]: pam_unix(sudo:session): session closed for user root
root@my:~#