Install NextCloud 11 on Fedora 25 with SaltStack
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@scottalanmiller said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@scottalanmiller said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
I needed to add "salt.domain.com" to /etc/hostname
Firewalld is still blocking access, did I somehow miss that setting?
When I "systemctl stop firewalld" I am able to connect
Those settings are in the salt confi files.
OK, port 443 is already open (per config file)?
You copied the files instead of using Salt, though, right?
Yes I copied the 3 files.
Was that not the right way?This is the part that would have opened the firewall. Are you getting any errors when running the Salt state apply?
FedoraServer: firewalld.present: - name: FedoraServer - block_icmp: - echo-reply - echo-request - default: False - masquerade: True - ports: - 443/tcp
-
@scottalanmiller No errors, the install completes fine.
I'm doing this install on NC v12.0.3 (not 11.0.2)
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@scottalanmiller No errors, the install completes fine.
I'm doing this install on v12.0.3
And if you check
iptables -L
it doesn't show Port 443 as being open? -
@scottalanmiller Let me check, brb
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@scottalanmiller No errors, the install completes fine.
I'm doing this install on NC v12.0.3 (not 11.0.2)
o/s if Fedora 26
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@scottalanmiller No errors, the install completes fine.
I'm doing this install on NC v12.0.3 (not 11.0.2)
o/s if Fedora 26
That should be fine.
-
-
Yeah, port 443 is definitely missing.
-
@reid-cooper said in Install NextCloud 11 on Fedora 25 with SaltStack:
Yeah, port 443 is definitely missing.
Question is why?
The conf file "says" to open up 443? -
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@reid-cooper said in Install NextCloud 11 on Fedora 25 with SaltStack:
Yeah, port 443 is definitely missing.
Question is why?
The conf file "says" to open up 443?Don't know. But you can always open it manually.
-
@reid-cooper I know it can be done manually, but, it would be nice to find out if I messed something up!
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
The default zone for firewalld is public. If you change open a service or port in a different zone you have to tell firewalld to use that zone instead.
-
@stacksofplates said in Install NextCloud 11 on Fedora 25 with SaltStack:
The default zone for firewalld is public. If you change open a service or port in a different zone you have to tell firewalld to use that zone instead.
How do I do that?
Remember, this was a "copy/paste" operation of @scottalanmiller files.
"FedoraServer" is the zone used in the original files. -
@stacksofplates said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
The default zone for firewalld is public. If you change open a service or port in a different zone you have to tell firewalld to use that zone instead.
That is for CentOS. Default on Fedora is not public.
-
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
This is on Fedora, you said?
-
@reid-cooper Yes, this is on Fedora
-
Why is firewalld not using the "FedoraServer" zone as specified in the salt config ?
-
@reid-cooper said in Install NextCloud 11 on Fedora 25 with SaltStack:
@stacksofplates said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
The default zone for firewalld is public. If you change open a service or port in a different zone you have to tell firewalld to use that zone instead.
That is for CentOS. Default on Fedora is not public.
On the server default is public. On the workstation it's FedoraWorkstation.
These are default and haven't been modified:
-
@stacksofplates said in Install NextCloud 11 on Fedora 25 with SaltStack:
@reid-cooper said in Install NextCloud 11 on Fedora 25 with SaltStack:
@stacksofplates said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
@fateknollogee said in Install NextCloud 11 on Fedora 25 with SaltStack:
Changing the name: from "FedoraServer" to "public"...like so:
results in this:
Now, I can log in.
What am I doing wrong?
The default zone for firewalld is public. If you change open a service or port in a different zone you have to tell firewalld to use that zone instead.
That is for CentOS. Default on Fedora is not public.
On the server default is public. On the workstation it's FedoraWorkstation.
These are default and haven't been modified:
I'm building one from the ISO to check. 99% of my stuff is built with virt-builder so it is possible they changed the default zone in the image. The normal cloud image doesn't have firewalld installed so I can't check on my OpenStack images.