Federated blogging application (ActivityPub)
https://joinplu.me/
Best posts made by stoccafisso
-
Hiding Wordpress app login page create backup problem
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.
-
RE: New installation, not able to log in
@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
-
RE: Cloudron overrides iptables-persistent
@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
-
RE: New installation, not able to log in
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
Latest posts made by stoccafisso
-
RE: New installation, not able to log in
@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
-
RE: New installation, not able to log in
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
-
RE: New installation, not able to log in
@robi I am using it on the dashboard (main) domain, on a subdomain
-
RE: New installation, not able to log in
@rmdes I chose to have the app have its own usermanagement, so LDAP should not be involved?
-
RE: New installation, not able to log in
@robi Yes
Tried now using a different subdomain, still same problem.
-
RE: New installation, not able to log in
I have tried using Chrome, Firefox and Brave browser. No login
-
RE: New installation, not able to log in
Thank you, I have tried reinstalling, but problem persist. Still not able to login using "root" and "changeme".
-
RE: New installation, not able to log in
Hi, and thanks for helping
Here is the log output:
Nov 07 16:54:00 [video.xxx.xx:443] 2020-11-07 15:54:00.182 info: 172.18.0.1 - - [07/Nov/2020:15:54:00 +0000] "GET / HTTP/1.1" 200 3921 "-" "Mozilla (CloudronHealth)" Nov 07 16:54:00 Nov 07 16:54:09 [video.xxx.xx:443] 2020-11-07 15:54:09.374 warn: Login error. { Nov 07 16:54:09 "err": { Nov 07 16:54:09 "statusCode": 400, Nov 07 16:54:09 "status": 400, Nov 07 16:54:09 "code": 400, Nov 07 16:54:09 "message": "Invalid grant: user credentials are invalid", Nov 07 16:54:09 "name": "invalid_grant", Nov 07 16:54:09 "stack": "invalid_grant: Invalid grant: user credentials are invalid\n at new InvalidGrantError (/app/code/server/node_modules/oauth2-server/lib/errors/invalid-grant-error.js:27:14)\n at /app/code/server/node_modules/oauth2-server/lib/grant-types/password-grant-type.js:94:15\n at tryCatcher (/app/code/server/node_modules/bluebird/js/release/util.js:16:23)\n at Promise._settlePromiseFromHandler (/app/code/server/node_modules/bluebird/js/release/promise.js:547:31)\n at Promise._settlePromise (/app/code/server/node_modules/bluebird/js/release/promise.js:604:18)\n at Promise._settlePromise0 (/app/code/server/node_modules/bluebird/js/release/promise.js:649:10)\n at Promise._settlePromises (/app/code/server/node_modules/bluebird/js/release/promise.js:729:18)\n at _drainQueueStep (/app/code/server/node_modules/bluebird/js/release/async.js:93:12)\n at _drainQueue (/app/code/server/node_modules/bluebird/js/release/async.js:86:9)\n at Async._drainQueues (/app/code/server/node_modules/bluebird/js/release/async.js:102:5)\n at Immediate.Async.drainQueues [as _onImmediate] (/app/code/server/node_modules/bluebird/js/release/async.js:15:14)\n at processImmediate (internal/timers.js:456:21)" Nov 07 16:54:09 }