http://ubismartbackend.com/Test123 gives a 404.
I'm running commands as an admin in Windows Command Prompt
http://ubismartbackend.com/Test123 gives a 404.
I'm running commands as an admin in Windows Command Prompt
OK. I don't see that test file either.
In your apache VirtualHost, you have ServerName ubismartbackend:5000
Normally the port is left off with name based virtual hosts. Can you try removing the :5000
from the name and restarting apache.
I deleted the ":5000" in
c:/apache24/conf/extra/httpd-vhosts.conf
then ran
httpd -k restart
Still 404's.
Let's confirm the test file. Can you show output of this:
dir c:\users\administrator\desktop\app\ubismartbackend\Test*
OK. Before we start looking at logs can you try changing the forward slashes to a backslash in your DocumentRoot folder. I don't use Windows/Apache myself so can't test but I see other examples online using Windows backslashes
\http://ubismartbackend.com/Test123
except the base URL is forbidden now?
c:/apache24/conf/extra/httpd-vhosts.conf looks like this
I need to step away for a bit but please show the renewal conf file I asked about earlier.
Also, what about this command
certbot certonly --webroot -w "(your path)" -d ubismartbackend.com -v --dry-run
Ok! Thank you so much for all of your help! Where is the renewal conf file?
\certbot\renewal\ubismartbackend.com.conf
This one
Ok. I see you used the standalone option in the past so your renewal conf uses that for "renew" command. It won't work with apache running and standalone is harder to use with web servers in general. So, we want to change that.
Your dry-run test of this worked. So, try this command again but leave off --dry-run. That should get an actual cert and update the renewal conf file to be webroot.
certbot certonly --webroot -w "(your path)" -d ubismartbackend.com
Do I need to manually install this cert to Apache? Ubismartbackend.com is still giving me 403
C:/Apache24/conf/extra/httpd-ssl.conf
@rg305
Please show the file:
C:/Apache24/conf/extra/httpd-ssl.conf
I restarted the Apache and my app is back online!
Make sure IIS
is disabled - that it won't try to start on reboot.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.