Recent content by SASolut

...that's what reverse proxies do, though. A reverse proxy is a server that sits in front of webservers and forwards client requests between those servers. I don't want a dedicated IP address for a subdomain, that's not even what reverse proxies do. In addition, it is the nuances of trying to...

That's for changing the webserver from apache to nginx_apache...now that I've done that, I'm trying to set up a reverse proxy from my server running DirectAdmin to a different server at a different IP address, so that clients can go to a subdomain without having to type in the IP address of a...

I am attempting to set up a reverse proxy using NGINX, pointing toward my host server from my DirectAdmin server. This is what I have set up in /etc/nginx/nginx-includes.conf: server { listen 80; server_name da.server.tld ; location / { proxy_pass https://ipaddress:4085/ ...

This is so weird. Certificate Error - https://mydomain.com/ (certificate shows for hostname) Apache is functioning normally, despite force-redirect enabled it won't redirect to https - http://mydomain.com/ Working fine (doesn't redirect, SSL set for mydomain.com) - https://mydomain.com:2222...

That's what I thought. I had a certificate for the domain, and the command I ran using the hostname instead, but it seems to have applied the hostname's cert for the domain too. I then tried to re-apply a new LE certificate to the domain (with wildcard) but unfortunately that did not change...

Uh oh...I think either I messed something up or the commands did. So I used the commands, but now the domain itself has an invalid certificate because the certificate is set for the hostname specifically. :O

Done, it's good now. Thanks for the help.

I used the built-in feature in the user panel for Let'sEncrypt SSL, using wildcard attribution. Should I still run the commands listed above, or does this shed light on another issue? There is no force encrypt option in my conf file.

I'm having trouble forcing SSL use on DirectAdmin. My primary domain is set up to use SSL and works, but if I try to connect to port 2222 it will ONLY connect via HTTP, not HTTPS. I feel like I had this problem before but I only recently returned to the IT world.

I completed your steps and it installed correctly, or at the very least it didn't return the same error. My network was disconnected after install. I checked in nmtui and found that a second network device was created using the same name as the first. This had the proper IP address, but no...

I know there's like 200 threads about this, but I can't find any with a viable fix. I've checked my license to ensure the OS is set properly (CentOS 8) as the link the error showed suggested I do. From what I can tell, not having a resolved hostname won't stop the installation but that may have...