Internal server error after installing on RHEL8

Get Help
21

Maybe - but you need the root certificate to be in the chain. I.e., apache has to recognize your self signed certificate’s root as being a certificate authority. I believe that’s just moving files around and making sure apache can read those files.

We do require SSL by default, but you can add these initialziers (as described in this ticket) to bypass that.

Lastly - let’s encrypt certificates are free work really well, so I’d also through that out there as an option.

1 Like
22

Many thanks, @jeff.ohrstrom

I have followed issue #1193 and finally succeeded.

I believe that SSL is a better choice.
Well, I am not sure that Let’s Encrypt works for private IP addresses and private domain names.

I would like to use Open OnDemand for teaching purposes. The students prefer clicking the mouse on the web interface to the traditional cmd line mode. The open OnDemand is awesome.

In my case, all the servers and laptops work on a private LAN. We do not have an internet connection. I am wondering if I can deploy Let’s Encrypt SSL for our servers. Or, if the SSL were a must-have, the self-signed cert would be the only choice? Sorry, this is the first time I have tried to set up an HTTP service. I am not quite familiar with TLS/SSL stuff.

By the way, restarting the HTTP server is not adequate.
Reboot the server instead.
You’d better drop all the cookies and cache for your browser, too.

23

On a private LAN where everyone (clients included) are on the LAN, plain http may be OK. I wouldn’t recommend it, because someone can catch that traffic (which could include passwords).

It seems to me that you need to reach out to a system administrator or someone who can setup that certificate.

I know as a user accepting a self signed certificate from something that’s supposed to be legitimate is off putting. Meaning - I myself would likely not accept it and ask someone directly what’s going on.

For Let’s Encrypt - I believe you would need internet connectivity as well as a valid CNAME for your machine (which it sounds like you don’t have internet connectivity) because it generates the certificate but also validates it.

Sorry, none of them seem like good options for you. Again, I’d suggest connecting with someone else at your site who may know how to resolve this with your sites constraints.

24

Thanks, @jeff.ohrstrom .

I tried another solution.
I configured httpd only to allow access from a particular LAN. And this specific LAN is powered by a VPN tunnel.

All users should start the VPN client first. All other connections are denied.

25

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.