@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 
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
@robi I am using it on the dashboard (main) domain, on a subdomain
@rmdes I chose to have the app have its own usermanagement, so LDAP should not be involved?
@robi Yes
Tried now using a different subdomain, still same problem.
I have tried using Chrome, Firefox and Brave browser. No login
Thank you, I have tried reinstalling, but problem persist. Still not able to login using "root" and "changeme".
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 }
Hi
Just installed PeerTube, and tried to log in as per "First Time Setup" instructions
username: root
password: changeme
But it says: "incorrect username or password"
Anyone experienced this, and know what to do?
EDIT: Sorry! Taking question elsewhere as it was not actually on topic. Sorry again.
I just played a little with installing Plex. I see it like to create some media directories in /opt/something and copy all the mediafiles there.
I want my media to stay where it is, and not be copied or moved anywhere else. If copied it will double my 600GB media to a total of 1200GB.
Maybe Plex is not for me. Or is there some other way to have Plex serve media from their current location, without copying or moving it?
@tadeas Hi, could this be something useful? https://cloudron.io/documentation/storage/#move-the-data-directory-to-another-location
@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
I came to think about something like this:
There are probably much better ways to do it, but at least I am trying to think out a possible solution. But how to code that script and get it to do the stuff I want? Anyone able to help?
Hi all
I need to have a few extra ports open on my home theater computer, which has cloudron installed as the "brain" for web-apps (nextcloud).
(So far I could not detect any conflict between cloudron and the other extra serverapps that is in need of these ekstra open ports (Virtualbox and its VM's))
I have added these ekstra ports in iptables and saved the configuration with iptables-persistent
But when server/cloudron is restarted, cloudron overrides my iptables-persistent settings and clean out my extra iptablerules.
How can I get cloudron to respect my extra iptables rules, and not wipe them every reboot/restart?
@nebulon Thanks a lot. NextCloud app installed. Now continue testing
@nebulon OK, new installation tested. Fresh Ubuntu 18.04 server Virtualbox clone, then installed fresh Cloudron. Cloudron ID is exactly the same id as previous installation (d781350d-8cc0-4d73-85a6-5214430500b8)
I did not change any VirtualBox "hardware" settings. Maybe I should try again, different RAM and different HD size?
BTW, all test installations have been configured for the same domain. Dont' know if that has anything to do with creating this odd problem?
Maybe I could have avoided these problems if I had uninstalled the installed apps in the first cloudron, before I deleted it. But main problem would still be there, then maybe for others to discover.
@nebulon These testinstallations are fresh. I have a Virtualbox Ubuntu18.04 clean server guest OS, which I clone when I need it, and then - after the cloning process - install a fresh Cloudron on it. When something goes wrong, I delete the guest OS, start a new clone, and do again a fresh installation of Cloudron. So I can not see how they should get the same cloudron id?
I'll make a note of the current cloudron id, and then do a fresh install, and then we see if it gets the same id as the previous one. I'll report back when done.
What conditions generate the Cloudron ID? Is it the hardware setup? If so the hardware setup are the same for each VBox server. Maybe I need to slightly alter the harddrive size for each new testinstallation?