Just added a new section about deploying / updatin...
# lucee
z
Just added a new section about deploying / updating lucee on firewalled servers https://docs.lucee.org/guides/deploying-lucee-server-apps.html#firewalled-servers I updated the commons-compress library due to a CVE which cased in place, aka .lco upgrades to fail on firewalled servers https://dev.lucee.org/t/latest-snapshot-is-failing-to-deploy-with-java-net-sockettimeoutexception-connect-timed-out/13034
👍 1
✔️ 1
⭐ 1
u
Thanks zack Should i need to get lucee 5.4
z
5.4.4.2-SNAPSHOT is the latest build with all the known 5.4 regressions addressed
m
Thank you for this Zac!
z
I'd like to be able to repo the timeout problem locally, simply shutting off wifi doesn't produce the same connection failures
m
Not sure if it is related or not but I have also shortened the request timeout in Lucee to 10 seconds on this server.
And also moved the WEB-INF folder outside of the web root.
z
those timeouts don't apply to bundle downloads, we did add a shorter timeout to solve firewall connection hangs
👍🏼 1
the web-inf folder is a good move, some people mis configure and expose it via the web
m
unrelated question - for Lucee installs are the web server's web root (IIS) and the tomcat server's web root usually set to the same folder? On Adobe CF I'm used to having separate web roots for Tomcat and the web server. Just curious of your stance on that?
z
so with 5, we have multiple contexts, with 6 there's single mode
end of the day, whatever works 🙂
the nice thing about leaving the port 8888 server there is you can access the admin on that port if you want to without worrying about webserver rules
💯 1
m
understood. Thanks again Zac for all of your help so far.
for admin access is exactly why I do that
also not exposed to the internet. local net only