b4bblefish
Dabbler
- Joined
- Sep 15, 2017
- Messages
- 15
Hi everyone,
I'm running Freenas 11-U3 and Nextcloud 10.0.1 plugin and trying to get TLSv1.1 and TLSv1.2 working on my Nextcloud plugin. However it looks like if I add those to my httpd-ssl.conf file I get an illegal protocol error on apache startup. I saw this thread that says something about the version of openssl apache was compiled with in 2015: https://forums.freenas.org/index.php?threads/owncloud-and-tls-1-1-1-2.30362/
Is that still the case? If so since it seems like using plugins is a huge PITA how would I route traffic from host nginx to a jail I make if I want to setup apache / nextcloud myself? When I install a plugin requests are automatically routed to the jail when I hit the jail's IP. But if I install apache inside a random jail it tries to bind to the same ip as the host instead of the ip of the jail. Ex... if i bind apache to port 8080 in my jail I can only reach it at host.ip:8080 instead of jail.ip:8080.
Also as a side question, why don't freenas plugins register apache as part of the services started up. I see the httpd process running, but
Thanks!
I'm running Freenas 11-U3 and Nextcloud 10.0.1 plugin and trying to get TLSv1.1 and TLSv1.2 working on my Nextcloud plugin. However it looks like if I add those to my httpd-ssl.conf file I get an illegal protocol error on apache startup. I saw this thread that says something about the version of openssl apache was compiled with in 2015: https://forums.freenas.org/index.php?threads/owncloud-and-tls-1-1-1-2.30362/
Is that still the case? If so since it seems like using plugins is a huge PITA how would I route traffic from host nginx to a jail I make if I want to setup apache / nextcloud myself? When I install a plugin requests are automatically routed to the jail when I hit the jail's IP. But if I install apache inside a random jail it tries to bind to the same ip as the host instead of the ip of the jail. Ex... if i bind apache to port 8080 in my jail I can only reach it at host.ip:8080 instead of jail.ip:8080.
Also as a side question, why don't freenas plugins register apache as part of the services started up. I see the httpd process running, but
service apache24 stop doesn't work since it can't determine if the service is running. Only stopping the plugin lets me start the service since the ports get unbound in the startup script.Thanks!
Last edited:
