Connection problem with HTTPS Help

[Itay1778]

OK, then your remaining tasks are to get a certificate and to configure Apache to use that certificate. Let's see where Apache's looking for the certificate files right now. In your jail, do ls -l /usr/local/etc/httpd/conf/ and
ls -l /usr/local/etc/httpd/conf.d/, and post the output here.

Code:

[root@nasla ~]# ls -l /usr/local/etc/httpd/conf								 
ls: /usr/local/etc/httpd/conf: No such file or directory						
[root@nasla ~]# ls -l /usr/local/etc/httpd/conf.d							   
ls: /usr/local/etc/httpd/conf.d: No such file or directory					 
[root@nasla ~]# 

 

[danb35]

IN YOUR JAIL.

 

[Itay1778]

Is this a good guide to what I need or is it anything else?
https://forums.freenas.org/index.ph...ficates-for-freenas-using-lets-encrypt.55276/

 

[Itay1778]

IN YOUR JAIL.

what do you mean?
It is not through the shell?

 

[danb35]

It is not through the shell?

Yes, it is through the shell--in the jail (and if you're using the shell button in the web GUI, don't--it's not fit for anything except, maybe, an odd command or two). You must run the commands in the jail. Running them at the root of your NAS won't work.

https://forums.freenas.org/index.ph...ficates-for-freenas-using-lets-encrypt.55276/

No, it is not a good guide for what you need. It's one way (though not an optimal way) to get a cert for your FreeNAS server itself (a better way is here), but that doesn't do anything for your Nextcloud instance.

 

[Itay1778]

Yes, it is through the shell--in the jail (and if you're using the shell button in the web GUI, don't--it's not fit for anything except, maybe, an odd command or two). You must run the commands in the jail. Running them at the root of your NAS won't work.

Right now I'm up to now used in all the commands given to me through the FreeNAS UI shell and it's not there then where exactly to put them, I do not quite understand what you mean jail shell please specify

 

[danb35]

If you're starting with a plugin and trying to hack Let's Encrypt into it, and you don't understand how to run commands in the jail, I'm afraid you have a lot of research to do. You'd probably be better off scrapping the plugin installation and doing a manual installation instead; this thread appears to have pretty thorough instructions on the process.

Edit: or a better idea yet might be to wait and see what @xCatalystx comes up with as an iocage setup script. You'll ultimately need to move your jails to iocage anyway, so doing it early on might be better.

 

[Itay1778]

If you're starting with a plugin and trying to hack Let's Encrypt into it, and you don't understand how to run commands in the jail, I'm afraid you have a lot of research to do. You'd probably be better off scrapping the plugin installation and doing a manual installation instead; this thread appears to have pretty thorough instructions on the process.

Edit: or a better idea yet might be to wait and see what @xCatalystx comes up with as an iocage setup script. You'll ultimately need to move your jails to iocage anyway, so doing it early on might be better.

I can not reinstall the plugin for personal reasons

 

[Itay1778]

But really I do not understand what the problem is just to set https it so hard?

 

[danb35]

You already have https set up. What you don't have is a trusted certificate. And no, it isn't so hard, if you have some idea of what you're doing at the command line, how jails work, and how TLS works--but it sounds like you're missing at least two of those things.

I can not reinstall the plugin for personal reasons

Then you're going to be stuck with a Nextcloud installation that's three major releases out of date.

 

[Itay1778]

You already have https set up. What you don't have is a trusted certificate. And no, it isn't so hard, if you have some idea of what you're doing at the command line, how jails work, and how TLS works--but it sounds like you're missing at least two of those things.

Then you're going to be stuck with a Nextcloud installation that's three major releases out of date.

I need to know just where and what to type in the command line so you can bring me a guide and explain to me where to type it because you said it was not through the UI shell so you can bring me an orderly guide for the purpose I need and tell me where to type ??

 

[Itay1778]

Will vpn also protect my connection as Https at least similar?

 

[Itay1778]

You already have https set up. What you don't have is a trusted certificate. And no, it isn't so hard, if you have some idea of what you're doing at the command line, how jails work, and how TLS works--but it sounds like you're missing at least two of those things.

Then you're going to be stuck with a Nextcloud installation that's three major releases out of date.

Look, I know I'm asking too much, but I'm begging for help
So maybe you connect remotely and set up the HTTPS I will give you all the details you need
Please I need help(:

 

[Nick2253]

set up the HTTPS

Like we've both said, you've already got HTTPS set up. Your connection is already encrypted. The only problem you have is an unsigned certificate versus a signed certificate. Browsers should allow you to easily pass through this. If you are having a problem with accepting the certificate, search for "<browser name> self signed certificates".

Look, I know I'm asking too much, but I'm begging for help

There are lots of resources to help you accomplish exactly what you want done. For example, the official FreeNAS documentation provides multiple ways to connect to a jail. A Google search for "freenas jail" would have brought you directly to that documentation if you didn't think to look there in the first place (which you should, because it's really good documentation).

 

[Itay1778]

Like we've both said, you've already got HTTPS set up. Your connection is already encrypted. The only problem you have is an unsigned certificate versus a signed certificate. Browsers should allow you to easily pass through this. If you are having a problem with accepting the certificate, search for "<browser name> self signed certificates".


There are lots of resources to help you accomplish exactly what you want done. For example, the official FreeNAS documentation provides multiple ways to connect to a jail. A Google search for "freenas jail" would have brought you directly to that documentation if you didn't think to look there in the first place (which you should, because it's really good documentation).

Although I use http at the moment my connection is encrypted like https just need a certificate ??

 

[Nick2253]

Although I use http at the moment my connection is encrypted like https just need a certificate ??

I'm not sure if there is a language barrier here, because I feel like this has been pretty thoroughly explained.

If you connect via HTTP, there is no, none, zip, zero, nada encryption. Totally exposed to the world. If you connect via HTTPS, then your connection is encrypted. You've explained here that HTTPS is working 100% correctly. The error message you are getting is related only to the certificate (because it is self signed), and in no way indicates any problem with HTTPS.

Again, just to be clear: if you connect via HTTPS with a self-signed certificate, your connection is still encrypted.

If you don't understand how the Internet's PKI works, you really need to do some reading. You are getting a warning in your browser because your browser cannot verify the authenticity of the certificate. This is expected with a self-signed certificate. Again, if you were having a problem with the HTTPS connection, you would be getting a different error message.

 

[Itay1778]

Yes, I thought so.
In any case, because I have trouble installing what I wanted, I will simply add the certificate to the browser
Thank you Nick2253 and danb35 for the help of both of you although i could not install what i wanted yet i learned but thank you very much for the help i know was not easy

Itay

 

[Itay1778]

Thank you very much for both of you. It would not work if you did not explain to me some important things.
The additional details in my browser:
The page you are viewing was encrypted before being transmitted over the Internet. Encryption makes it difficult for unauthorized people to view information between computers. The likelihood that someone could read this page while it was transmitted over the network is very low