Cloudron Forum

i've been able to remount the backup and storage volumes now, it must have had to do with the Hetzner DNS outage. Thanks for your help @joseph

@joseph i'm able to ping the storagebox succesfully from the cloudron server as well as my local machine.

I've got the same issue on version 8.0.3, but have not been able to remount my Hetzner Storagebox via CIFS or the volumes on the same storage box via SSHFS. @staff any suggestions how to fix this?

I'm not sure if they have all the features that you're interested in but Chatwoot and Freescout on Cloudron might fit the bill.

I've used Missive quite a bit, it's not open source or self-hosted, but is a pretty good service.

@girish I've created support tickets and given you access. Thanks for looking into this.

@girish thanks for the response.

the server_name field was missing from the config file for some reason. i added the field at the top of the file and restarted the app, but am still getting these errors in the matrix app log:

Healtheck error: Error: connect ECONNREFUSED 172.18.19.36:8008

OSError: [Errno 30] Read-only file system: '/app/code/media_store'

the peer tube app does have a /app/data/storage/logs/ directory with log files in it. this app is still not responding as well. i can see this in the error logs:

errno: -2,

The Synapse and PeerTube apps have stopped working on our Cloudron. This happened after a reboot for system updates, and it's a bit of mystery why they should suddenly get misconfigured. I've tried several restarts and restoring from a backup, but it hasn't fixed the issue. Renewing Certs and DNS hasn't helped either.

The logs for the Matrix/Synapase show these errors:

Healtheck error: Error: connect ECONNREFUSED 172.18.19.36:8008=> Starting synapse
Error in configuration:
Missing mandatory server_name config option.

The logs for PeerTube shows these errors:

Healtheck error: Error: connect ECONNREFUSED 172.18.16.78:90002022-10-16T08:21:42.000Z ==> Starting PeerTube
throw err;
^
ENOENT: no such file or directory, mkdir '/app/code/server/storage/logs'

Any help to troubleshoot and get these apps back running would be much appreciated.

@nebulon Thanks, that worked a treat. I had tried 443 as the port previously, but that didn't work possibly because I didn't use 'https' in the url. Port 2283 was specified on the Immich Github page.

Thanks for packaging this! It looks like it already is/and could become a great photo app. I was just trying to get an andoird mobile app connected, but it doesn't seem to be able to login. The server endpoint I'm using is http://[cloudron-app-location]:2283/api

Has anyone had any luck yet with using the Immich mobile app?

I also had the same error running Cloudron 7.2.2, and restarting the mail service solved the issue.

i can confirm that the order of the steps @onlybro describes work to enable video posting. so i guess including the config line by default as @robi suggests, would make it work for everyone?

@onlybro it worked from the web interface initially, but now only from a client app

@onlybro yeah, you need to add that to the config. here's a screenshot for reference - Screenshot_20210410_225929.jpeg

but as i mentioned on the other thread, this doesn't seem to work for me now, in order to create video posts.

@onlybro i had to reinstall the app, and tried to do the same steps. but for some reason i'm not able to post videos now from a browser.

the funny thing is that posting videos from the fedilab app on android works. i guess the app is just not ready for prime time yet?

@onlybro i'm not sure what the reason for it not working for you might be. you could perhaps try restarting the app if you haven't already, increase the ram allowance, and try creating the post from a different browser. the file size of the video could also be a factor.

so just to update, I got the video working by adding the below line to the env.production (turns out it was just a syntax error ) and then running 'php artisan config:cache' in the terminal -

MEDIA_TYPES=image/jpeg,image/png,image/gif,video/mp4,video/mpeg,video/3gpp,video/quicktime

instagram import still isn't working for me (this might be a deal breaker for people looking to move over). and the way the federation works doesn't seem to allow you to find people and posts on other instances easily yet.

@nebulon i upped the RAM allowance to 1.24 GB, but this was not based on any testing and was just to see if it works.

i like the look of the app, and the fact it is it a federated alternative to instagram. but at the moment, especially without the video posts working, i don't know how much real world use it has. and that's a pity really.

increasing the RAM seems to sort out the errors above (unless it's just a coincidence).

i'm unable to create video posts videos or import from instagram, after adding the below to the config file:

MEDIA_TYPES="image/jpeg,image/png,image/gif,video/mp4"

IMPORT_INSTAGRAM=true
IMPORT_INSTAGRAM_POST_LIMIT=100
IMPORT_INSTAGRAM_SIZE_LIMIT=5000

I'm trying to get Pixelfed working, but there seems to be a few glitches.

I think federation is working, because I'm able to follow:
doodlemania@pixels.thedoodleproject.net and girish@pixelfed.social.

But the Discover page (/discover) is blank and also the following errors are being generated on the failed jobs page -

Anyone have ideas or tips on how to get it to work?

@p44 thanks, it works great.