Posts made by CrimsonKidA

Would I need to add something to the salt script to enable the "LDAP user and group backend" v1.1.2 app for NextCloud? I want SSO for our AD users, but NextCloud says "This app cannot be installed because the following dependencies are not fulfilled:
The library ldap is not available."

...in that case I may just use 443, yeah.

Oh very cool! I did not know that

@scottalanmiller said in Install NextCloud 11 on Fedora 25 with SaltStack:

onse I understand. Why port 80 though?

Not sure if it will get used outside our LAN yet. If so, I will close 80 and purchase an SSL cert.

@scottalanmiller Thanks so much, Scott! Working perfectly now! Personally, I want a PING response, plus port 22 and 80 open, so I'm going to tweak IPtables, but it is coming back up after rebooting the VM.

@scottalanmiller Thanks, I'll look at making a cron job for it to run at boot. I'm having to manually disable the firewall at each boot too, so that will need to be added. Salt master and minion are starting up on their own now, so that's good.

@scottalanmiller Well, it doesn't lose my NextCloud config (I changed the admin PW) but Apache2.4, Salt (master and minion) and NextCloud are just not auto starting up. I've set the salt services to auto-start up, so I'll see if that's all it needs...

Thanks again, Scott! Just one last question: how do I get this to "stick" after a reboot? It seems to be reverting back to having nothing installed after I reboot the Fedora Svr VM...

@scottalanmiller Thanks, Scott. I ran the your final command again and it worked this time: Succeeded: 19 (changed=5)! The firewall seems to be too aggressive, so I just turned it off since this will be LAN-use only (at least for now).

The script seemed run fine, but I still have no NextCloud installation. I thought it was just the firewall getting enabled in Fedora, but I turned it off and still nothing is there on 443 at the IP (other than Cockpit at 9090 of course).

...just CD'd back to /srv/salt and your scripts are working now!!

@scottalanmiller Perfect, thanks. I just added '127.0.0.0 salt' to my /etc/hosts file and that got the DNS issue cleared up. But then the key was still not accepted. Got that sorted by running:
salt-key -A
from directory /etc/salt

@scottalanmiller Thanks, I have DNS lookup failures for 'salt' and master hostname 'salt' not found as a result.

@scottalanmiller Afraid not. I did find where to change the salt master in the /etc/salt/minion file (line 16), so I un-commented it out and changed that to master:localhost and restarted the salt-minion service again, but no change. Also tried restarting salt-master service.

@scottalanmiller Thanks, I just appended it on to the end of /etc/salt/minion via Nano and restarted salt-minion service. No change though...?

@scottalanmiller Sorry, I don't follow. I only have one VM and it's the Fedora 25 Server. It's running everything.

@scottalanmiller [root@NextCloud salt]# salt-key --list-all
Accepted Keys:
Denied Keys:
Unaccepted Keys:
Rejected Keys:

Hey Scott, Drew here (CrimsonKidA) from SW. I think there might be something wrong with my Salt Master install. The salt-master service doesn't auto start at boot, so I manually start it. Also, it didn't seem to make /var/cache/salt/master either, so I manually created it. When I try to run your last command here, this is what I get:
[root@NextCloud /srv/salt]# salt 'NextCloud.ourdomain.com' state.apply nextcloud
No minions matched the target. No command was sent, no jid was assigned.
ERROR: No return received

Any ideas? Thanks.