IIS 7 and Above
IIS default homepage missing, replaced by organization website and ma...
Last post Mar 22, 2019 06:28 AM by KabzJoe
Mar 21, 2019 06:59 AM|KabzJoe|LINK
This thread might be lengthy but i need your help trying to figure out the why my php website page "won't be found".
I work for an international organization that has it's HQ and central domain(myorganization.org) in the US. I am an IT assistant in one of the countries(UG) and want to add a website to run alongside the subdomain (site1ug.myorganization.org).
site1ug.myorganization.org was mapped to the public ip and the localhost(IIS default). I'd like to add a website (site2ug.myorganization.org) to run along side
These are the instructions i followed.
4.Install and configure PHP (7.2.8)
While testing the site off the production network i was able to run the website through (http://localhost:2255/site2ug/) but i can't do that now since the localhost is mapped to site1ug.myorganization.org
NOW on the production network, I went as far as 11 and also configured SSL certificate for it. Upon browsing the site "PAGE cannot be found!" EVEN when i left the host header empty, it returns the same ERROR.
PS: I haven't added a dns record for it yet(Have to wait for HQ's permission).
What i need to understand; is the DNS record missing the reason i can't browse the site? Or I'm i missing something?
Mar 21, 2019 03:18 PM|Rovastar|LINK
Mar 22, 2019 06:25 AM|KabzJoe|LINK
After hours of troubleshooting I found a solution...
I reinstalled PHP, MSSQL drivers.
-created a sessiondata folder inC:/php/sessiondata
I then edited the php.ini file
-added the path for session_save
-added the extension=php_sqlsvr
After this i added the website in IIS and edited the host header for http via port:80 and https via port:443 i also added the SSL certificate.
I then edited the server host file and added both site1ug.myorganization.org and site2ug.myorganization.org mapping them to the same ip address.
I realized that if i'd only add site2ug.myorganization.org to the host file it'd cause site1 to go offline and this is because both use port:443 hence both need to be specified.
After this BOTH sites are working fine.
I hope someone else finds this useful incase they encounter the same.
Mar 22, 2019 06:28 AM|KabzJoe|LINK
Thank you Rovastar i did just that and it worked. I can now access it on the local network and soon as HQ adds it to the DNS the world will be able to see this.