Cloudron Forum

I'm trying to install Bluesky on my server, but I can't get it to work. When I run the installer, I get this error :
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

also, when I go to the link, I see Cloudron's error message instead: You are seeing this page because the DNS record of bluesky.cocamserverguild.com is set to this server's IP but Cloudron has no app configured for this domain.

okay I found the solution :
In Postgres, you have to set "storage" to "0" (in videoStreamingPlaylist) with the video id

the second link (everything on the second link)

it worked! ty!

@jdaviescoates that's what I had done before deleting the bucket, but since some videos weren't working and I had manually downloaded everything, I decided to manually put the videos that weren't working but that weren't loading on Peertube

But can "Update object storage URLs" be used to store a local video URL?

My old videos were on an S3 server. The files were moved to the local server because I decided to host them somewhere other than the S3 server. The new videos and some videos that were on the S3 work, but on some videos Peerube tries to connect to the S3 server that no longer exists.

The video is in /data/storage/streaming-playlists/hls but Peertube is trying to load it from the S3 server. Is it possible to force Peertube to play local videos?

Hi! I tried but it's not working

because all the new posts work, just not the old ones

except 404 not found, I don't see anything weird. Is there a way to force the server to re-download everything?

Hello everyone.

The old images no longer load on my Mastodon instance (coming from other servers, not the local ones. It return 404 not found).

The recent images load and I would like to know if there is a way to correct the problem.

I'd like to point out that people who have this problem continue to send posts.

Hi!

I would like to know how to let the terminal connected. Without being reconnected (I would like to do something on one of my apps, but it takes 2 hours. The fact that the terminal reconnects stops the command, which prevents me from doing my command)

If I can run my commands and detach them from the terminal, it would be perfect

Thanks in advance for your help

Okay I saw an option "server doesn't support chown" something like that for backups. I activated that and it worked. I have a new question but I will open a new ticket.

Thanks for your help!

I used curlftpfs to mount my storage server

Hello!

I would like to know if it's possible to disable the chown command while making backups.

I have a storage server made for that but it's in ftp so it's unable to chown

mmmm I only see that my images take 9.31 GB and my local volume 241 MB... I don't know what's taking up so much space, honestly

all my services work with an S3 server behind them, so I doubt it has anything to do with media files (images/videos) of my services

@nebulon @joseph okay I did that but the system space always seems to be full. Also, I did the docker system prune command and nope, no reclaimed space

If it's just unused virtual space, how do I reduce this space to give it back to the system?

@nebulon hiya! Okay I tried to move it on /mtn/docker (I mounted my s3 server on it. Idk if that's the issue) but when I try to launch the service (Docker) I have that :

Sep 28 08:15:53 beige-beaver-45300 systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit docker.service has finished.
--
-- The job identifier is 1960 and the job result is done.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.service: Start request repeated too quickly.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit docker.service has finished with a failure.
--
-- The job identifier is 1960 and the job result is failed.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.
lines 3518-3546/3546 (END)
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: Stopped Docker Application Container Engine.
-- Subject: A stop job for unit docker.service has finished
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A stop job for unit docker.service has finished.
--
-- The job identifier is 1960 and the job result is done.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.service: Start request repeated too quickly.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit docker.service has entered the 'failed' state with result 'exit-code'.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: Failed to start Docker Application Container Engine.
-- Subject: A start job for unit docker.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit docker.service has finished with a failure.
--
-- The job identifier is 1960 and the job result is failed.
Sep 28 08:15:53 beige-beaver-45300 systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'.

When I remove the content in custom.conf, it works again

Hi! I saw today that my /var/lib/docker/overlay2 folder is 42 GB. Is there any way to free up space?

Thank you in advance for your answers

I forgot to update this topic, sorry. But the problem has been fixed (I changed the object storage server)

the information I sent above is more specific to the OS running Cloudron