Cloudron Forum

Federated blogging application (ActivityPub)
https://joinplu.me/

Hi team

It looks to me that cloudron packaged AzuraCast is the rolling release instead of stable. (I see it in the /admin/updates/ section.

Why not use the stable instead? There seems to be many bugs in the rolling release version that make it almost impossible to run a working radio station.

Any thoughts?

@nebulon said in Cloudron overrides iptables-persistent:

iptables-save >/etc/iptables/rules.v4

Thanks @nebulon , that may be the problem, as I initially only ran the command

iptables-save

instead of

iptables-save >/etc/iptables/rules.v4

(I followed this guide: https://linuxconfig.org/how-to-make-iptables-rules-persistent-after-reboot-on-linux)

Now the iptables rules (inkl custom rules) persist after reboot, but then again...cloudron has had no reason to do changes.

So I provoked it by installing another app (wordpress-app). A few seconds after installation it said wordpress was running, but I could not access it. A few seconds later I could. So it seems it is working. (Maybe I should have tried another app, with other ports)

@necrevistonnezr maybe you could also benefit from looking at iptables-persistent? https://linuxconfig.org/how-to-make-iptables-rules-persistent-after-reboot-on-linux

Hi all

In wordpress app I use a plugin to hide the login page /wp-admin and /wp-login.php. Accessing these pages will then give the user a 404

BUT, it seems cloudron is sending a form of beacon signal to the wordpress app login page, to figure out if the app is up working or not. As cloudron does not find the login page, it detect it as an error and state in the cloudron admin panel that the app is "Not responding", even though the wordpress app is running fine.

It may look like this also prevents cloudron from creating automatic backups of the app, even if it is configured to do so. Manual backup seems to work though.

@joseph if you read my opening post, you will see that I am fully aware of the procedure. However, in my case I can not export any backup from the old Wallabag, as I get export 500 error whatever way I try to export those more than 3000 stored articles. Thats why I created this post with request for help.

@girish said in New installation, not able to log in:

echo "changeme" | npm run reset-password -- -u root

Thank you @girish. I actually had a lot running on this cloudron, but could not get PeerTube to work even if I removed several other apps to free up memory.

But the above command for some strange reason fixed it and solved the problem. PeerTube is now working!

Thank you

Oh man, give us JAMS (JAMS - Jami Account Management Server)

Hold on a minute....seems like restore worked well after all....strange thing....I check it out and report back....

Problem solved. I deleted ALL config files and restarted the server.

Hi all

The default character limit for new toots is 500. But I would like to increase that limit for my special instance.

How can I do this? And hopefully make it a permanent change, not overwritten by updates?

Any help?

Hi all

Just discovered that my Wallabag app has version 2.4.1, so it has not been updated, even as I have it set to automatic update.

If I try to manually update it, it reports no new update to download. How can I make it update?

I have over 3000 articles in there, and it gives export 500 error when i try to export (any option), so I am not able to backup the articles and install a new updated version from scratch. So how can I do the update from 2.4.1 and still keep my articles? Is there a way to hack this manually? Or getting help from support directly on my cloudron server? (premium)

Hi @james

Now I see, it was just to skip the port 9090 behind URL. I didn't even consider it possible. Thank you, it worked now

Hi @girish

I tried installing PeerTube on your demo server, and was able to log in to PeerTube using "root" and "changeme".

Full log from my own installation is sent you at support@cloudron.io

Ahh...I see now that I missed a required MANUAL update long time ago.

But now I am stuck. Any idea what I can do?

Ahh...in Prometheus, just click "Status - Service discovery"

I did a brutal problemsolving hack, deleted Grafana and reinstalled it. Now it works.

I think it may have been the "Node Exporter Full" dashboard that was holding the old config in cache, I may have solved it just by deleting the Node Exporter Full and then reinstalled it.

@james and @joseph Thanks for helping