ejabberd would be freakin amazing!!
Best posts made by opensourced
-
RE: ejabberd - Robust, Scalable and Extensible Realtime Server using XMPP, MQTT and SIP
-
RE: Cloudron Backups on TrueNAS NFS mount
@opensourced nevermind, i figured it out!
Latest posts made by opensourced
-
Rocket.Chat push notifications not working - remoteIP wrong
I am running my instance of Rocket.Chat and still have not managed to get the push notifications working.
Around one month ago, I have opened a thread in the RC forum, because I thought the error i got was more relied to their side. As I am not getting an answer there, I decided to link this one here as well.
So I have set up my RC instance and I registered it on RC Cloud.
The Push Gateway is enabled and set to https://gateway.rocket.chat/.
I installed the RC apps on an iPhone, an android phone as well as on my Macbook. Finally I also managed to send test-push-notifications via the dedicated button. It tells me that it has successfully sent a test notification to 1 device. However, having checked the settings and permissions on the phones, I to not receive any notification on either of them.
When I look at the Log I can see two suspicious entries. What is the remoteIP? The VM of the RC is NATed by a firewall and does have a dedicated public IP, which is obviously not the remoteIP. May that be the problem? How could I change this?
{"level":35,"time":"2021-11-01T09:15:10.813Z","pid":1,"hostname":"ca5sdgh54-1a8d-4564-b816-8d3e5edffd65","name":"API","method":"POST","url":"/api/v1/method.call/push_test","userId":"So49htrw","userAgent":"Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Firefox/91.0","length":"87","host":"rocketchat.foobar.com","referer":"https://rocketchat.foobar.com/admin/Push",**"remoteIP":"172.16.115.1"**,"status":200,"responseTime":67} {"level":50,"time":"2021-11-01T09:15:11.118Z","pid":1,"hostname":"ca35684-1a484-b816-8d3e5d65","name":"Push","msg":"Error sending push to gateway (0 try) -> {\"response\":{\"statusCode\":404,\"content\":\"404 page not found\",\"headers\":{\"access-control-allow-headers\":\"Content-Type, Authorization, Content-Length, X-Requested-With\",\"access-control-allow-methods\":\"GET, PUT, POST, DELETE, OPTIONS\",\"access-control-allow-origin\":\"*\",\"access-control-expose-headers\":\"Content-Type, Authorization, Cache-Control, Expires, Pragma, X-powered-by\",\"cache-control\":\"private, no-cache, no-store, must-revalidate\",\"content-length\":\"18\",\"content-type\":\"text/plain\",\"date\":\"Mon, 01 Nov 2021 09:15:11 GMT\",\"expires\":\"-1\",\"pragma\":\"no-cache\",\"x-powered-by\":\"Rocket Fuel and Rocketeers\",\"connection\":\"close\"},\"data\":null}}"}
The second entry I do not understand is this…
{"level":50,"time":"2021-11-01T09:11:15.118Z","pid":1,"hostname":"ca54-b816-8d3edffd65","name":"Push","msg":"Error sending push to gateway (4 try) -> {\"response\":{\"statusCode\":404,\"content\":\"404 page not found\",\"headers\":{\"access-control-allow-headers\":\"Content-Type, Authorization, Content-Length, X-Requested-With\",\"access-control-allow-methods\":\"GET, PUT, POST, DELETE, OPTIONS\",\"access-control-allow-origin\":\"*\",\"access-control-expose-headers\":\"Content-Type, Authorization, Cache-Control, Expires, Pragma, X-powered-by\",\"cache-control\":\"private, no-cache, no-store, must-revalidate\",\"content-length\":\"18\",\"content-type\":\"text/plain\",\"date\":\"Mon, 01 Nov 2021 09:11:15 GMT\",\"expires\":\"-1\",\"pragma\":\"no-cache\",\"x-powered-by\":\"Rocket Fuel and Rocketeers\",\"connection\":\"close\"},\"data\":null}}"} {"level":30,"time":"2021-11-01T09:11:15.119Z","pid":1,"hostname":"ca5e0f54-1a4d-4594-b816-8d3e5edffd65","name":"Push","msg":"Trying sending push to gateway again in 960000 'milliseconds'"}
Follow the thread here:
https://forums.rocket.chat/t/getting-push-notifications-to-work/12513Thanks in advance!
-
RE: ejabberd - Robust, Scalable and Extensible Realtime Server using XMPP, MQTT and SIP
ejabberd would be freakin amazing!!
-
RE: Grafana email alerts not working
@girish thanks a lot! I can confirm that its working now.
-
RE: Cloudron Backups on TrueNAS NFS mount
@opensourced nevermind, i figured it out!
-
RE: Cloudron Backups on TrueNAS NFS mount
@jdaviescoates So I took another approach and setup another vm running an nfs-server. With that advice i was ableto connect it to the cloudron.
@girish Next to the main cloudron instance (which is paid plan), i do have another cloudron instance running (free plan). On this one I am not able to connect the same nfs share. Is that feature only working for paid plans?
-
RE: Backup job killed my cloudron
I am working on get my FreeNAS NFS mount working for the backups, but that seems to be a bit difficult to get the permissions working.
If you have experience with NFS, you might have an answer on my problem here...
https://forum.cloudron.io/topic/5927/cloudron-backups-on-truenas-nfs-mount/3?_=1636891033300
However thanks!
-
Grafana email alerts not working
I configured a monitoring in Grafana and would like to make Grafana send me alerts via email.
When I add the notification channel in the Alert settings and try to send a test notification, i get an error. Any idea on how to fix this?
INFO[11-13|23:27:20] Sending alert notification to logger=alerting.notifier.email addresses=[root@mydomain.com] singleEmail=false Nov 13 23:27:20 EROR[11-13|23:27:20] Failed to send alert notification email logger=alerting.notifier.email error="Failed to send notification to email addresses: root@mydomain.com: unencrypted connection" Nov 13 23:27:20 EROR[11-13|23:27:20] failed to send notification logger=alerting.notifier uid= error="Failed to send notification to email addresses: root@mydomain.com: unencrypted connection" Nov 13 23:27:20 EROR[11-13|23:27:20] failed to send notification logger=alerting.notifier uid= error="Failed to send notification to email addresses: root@mydomain.com: unencrypted connection" Nov 13 23:27:20 EROR[11-13|23:27:20] Failed to send alert notifications logger=context userId=2 orgId=1 uname=root error="Failed to send notification to email addresses: root@mydomain.com: unencrypted connection" remote_addr=172.17.2.1 Nov 13 23:27:20 EROR[11-13|23:27:20] Request Completed logger=context userId=2 orgId=1 uname=root method=POST path=/api/alert-notifications/test status=500 remote_addr=172.17.2.1 time_ms=27 size=48 referer=https://grafana.mydomain.com/alerting/notification/3/edit
Thanks in advance!
-
Backup job killed my cloudron
A backup task was filling up the whole storage of my VM & killed the cloudron instance. I removed the backup in /var/backup and restarted the VM. cloudron showed me:
«You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.»
I checked the box status and all seemed good, however I didnt got it back to running. After trying some things, I recovered the whole vm from a backup.
How can i prevent this from happening next time?
-
RE: Cloudron Backups on TrueNAS NFS mount
@girish Thanks for the superfast reply! I checked the web and the TrueNAS Forum for a hint where I can change this setting. Didn't find it though. Do you have that information handy as well?
-
Cloudron Backups on TrueNAS NFS mount
So I am trying out the backup capability of cloudron using NFS shares. After setting up the NFS share on TrueNAS and opening the permissions, I managed to attach the share to cloudron.
However, the backup fails and I receive the following log message:Oct 30 12:52:49 box:backupupload v8 heap : used 22807312 total: 24461312 max: 4345298944 Oct 30 12:52:53 box:tasks 306: {"percent":93.30769230769232,"message":"Uploading backup 2M@2MBps (box)"} Oct 30 12:53:14 box:tasks 306: {"percent":93.30769230769232,"message":"Uploading backup 2M@2MBps (box)"} Oct 30 12:53:14 box:shell backup-snapshot/box (stdout): 2021-10-30T12:53:14.420Z box:backupupload upload completed. error: BoxError: Unable to chown:EINVAL: invalid argument, chown '/mnt/cloudronbackup/snapshot/box.tar.gz' at WriteStream.<anonymous> (/home/yellowtent/box/src/storage/filesystem.js:138:95) at WriteStream.emit (events.js:327:22) at finish (internal/streams/writable.js:657:10) at finishMaybe (internal/streams/writable.js:644:9) at internal/streams/writable.js:617:7 at WriteStream._final (internal/fs/streams.js:355:3) at callFinal (internal/streams/writable.js:610:10) at processTicksAndRejections (internal/process/task_queues.js:80:21) { reason: 'External Error', details: {} Oct 30 12:53:14 box:backups runBackupUpload: result - {"result":"Unable to chown:EINVAL: invalid argument, chown '/mnt/cloudronbackup/snapshot/box.tar.gz'"}
Cloudron was able to make a directory on the share, however, the owner of the file is «nobody».
Is this somehow related to the permission settings on TrueNAS?
Thanks in advance!