Hi Guys I have just watched a great tutorial: <h...
# lucee
c
Hi Guys I have just watched a great tutorial: https://dev.lucee.org/t/how-to-install-lucee-on-windows-2019-server-iis-video-tutorial It describes how to Install Lucee on Windows Server 2019. I am using Windows Server 2016. I have installed a standalone version of Lucee 5.3.9.166 with all the default settings, including the IIS connector/mod rewrite, checked. I have then added a website via IIS, using a binding of:
port: 80
ip: 127.0.0.20
host: foo<http://.bar.com|.bar.com>
In my host file, I have added:
127.0.0.20 <http://foo.bar.com|foo.bar.com>
Within the box [locally], when I navigate to:
<http://foo.bar.com|foo.bar.com>
It says:
Page not found
There is no IIS 500 message or Lucee error. :( Within the box [locally], when I navigate to:
<http://foo.bar.com:8888|foo.bar.com:8888>
Everything works? Do you know why? I haven’t tried the permissions LOCAL.SERVICE fix, shown in the video, because I am not sure it is entirely relevant to my problem. I haven’t removed that ISAPI module etc within IIS, which is also shown in the video. I must say, I have never had to remove anything from the Handler Mappings module? Why exactly is this being done? All the required BonCode mappings are in the Handler Mappings module, so I left it, at that? I really need this to work on port 80. Any ideas, on how to get: foo.bar.com To work on port 80?
By the way, I have not edited server.xml, except that I added a host entry for foo.bar.com. Although, I am not entirely sure this is required for non public facing websites. Please understand that this is a QA testing box, so the the QAs will RDP into the box and test inside the box.
I have compared the QA box server.xml with my VPS server.xml and it seems like Lucee [on Windows] uses the default Host context of:
Copy code
C:\inetpub
I reckon this might be a possible solution:
Copy code
<Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true" xmlValidation="false" xmlNamespaceAware="false">

   … mod_cfml.core valve

   <Context path="" docBase="D:\www" /> 

</Host>
I was hoping that the Lucee IIS connector, would have resolved all these issues. I was expecting to just add a new website to IIS, and Lucee would automatically connect on the port, specified within IIS binding?