i see....and if there's something that isn't covered there, specific questions are a lot more likely to get helpful answers than "please tell me how to do" something that's been extensively documented all over the web.
What I'm trying to achieve it's connecting to the server using https and getting the green lock symbol. The issue is I have no idea where to start and are what files I need to edit and put in those files. I have read where it states that you can force HTTP to https. I would like to achieve this to where I can access my nextcloud internally through the land using https as well as externally using my no IP given DNS. I am a novice when it comes to editing these configuration files but given the proper guidance I am willing to learn and understand what it is I'm doing so that I can advance on the newly giving skill set...and if there's something that isn't covered there, specific questions are a lot more likely to get helpful answers than "please tell me how to do" something that's been extensively documented all over the web.
That would be unusual. Can you complete a thought in a single post, rather than three or four?And I had to add some lines of code to the htaccess file
Yes I can. LOL. I was simply attempting to be descriptive of what I was trying to achieve. Though I admit I probably got a little bit carried away. With that said I'll post the errors in just a second or minute.That would be unusual. Can you complete a thought in a single post, rather than three or four?
If you're getting a red X when you're connecting via https, the system probably gave you some accompanying error message. If you'd share that message, it would help figure out what happened.
Header set Strict-Transport-Security "max-age=15552000; includeSubDomains; preloIt would also be helpful if you'd post what you added to .htaccess, and what (if anything) you changed in your web server's config files. Two websites that will help figure out what's going on with certificate errors are https://www.whynopadlock.com/ and https://www.ssllabs.com/ssltest/
That was a bad idea to add before you had SSL running properly, as it will have exactly the result you describe: you won't be able to use HTTP on that hostname any more.Header set Strict-Transport-Security "max-age=15552000; includeSubDomains; prelo
# line below if for Apache 2.2
<ifModule !mod_authz_core.c>
deny from all
It does matter in that it determines what changes need to be made to your web server's configuration files. Did you change anything there? If so, what?im running apache 2.4 but i guess it really didnt matter
Just added that nothing moreIt does matter in that it determines what changes need to be made to your web server's configuration files. Did you change anything there? If so, what?
That's probably your problem. Did you get the certificate already? What's the output ofJust added that nothing more
certbot certificates
? If you have the cert, you need to update your Apache config file(s) to point to that certificate and its corresponding private key.Ok I'm trying and will post the resultsThat's probably your problem. Did you get the certificate already? What's the output ofcertbot certificates
? If you have the cert, you need to update your Apache config file(s) to point to that certificate and its corresponding private key.