I've got a really weird issue going on with multip...
# lucee
d
I've got a really weird issue going on with multiple servers and Lucee 5.4.3.2. When I go to the Lucee Admin page, I'll get the login screen. However, once I enter the password my servers start returning a 404 error. Any attempt to get to the login screen after that will give a 404 error. If I restart Tomcat or clear the cookies, I'll see the login screen again, but any attempt to log in is just producing 404 errors. Has anyone seen this? /cc: @zackster
Ok, after some changing of my Nginx rules, what I'm seeing is that an attempt to get into the Admin is going to: lucee/admin/server.cfm?action=overview This is producing the following:
a
Could it be that your upgraded lucee has not been fully deployed? I had such issues when upgrading and tomcat not fully creating the deployments. What I usually do is (after backup becaue it will wipe out your admin setting) is stop tomcat, wipe /lucee-server/ and all the web-contexts in each wwwroot and restart Tomcat.
z
nah it's been deployed, coz you can see the admin, there is a heap of hardening in the admin with 5.4.3.2, this is tripping up somehow validating that the url.action, aka filename exists and is in the current folder
a
@zac But I swear, I've seen those type of errors before while I was developing my admin translation plugin. I have wiped out the server context and web contexts like a hundred times for testing, and I saw exactly that error being thrown when the template wasn't found. However, going to take a look right now!
Not on mine windows:
going to check my ubuntu box in a couple of minutes
@dswitzer I've just spun up my ubuntu. I can confirm it happened exactly the same that happened on your machine when upgrading to 5.4.3.2 WIHTOUT wiping out the "lucee-server" directory. If you stop Lucee, remove the "lucee-server" directory, end restart Lucee, everything works fine. This is something we should add to the Lucee Community Forum
However, you might need to backup your settings first
@dswitzer please wait with doing anything... we are investigating this.
d
What's really weird, is the problem will seem to eventually correct itself. I saw the issue on 2 different servers, with different two different web context and the problem eventually went away. Now, it's totally possible it went away because of something I did, but I'm not sure what I changed. What's odd is that other pages in the admin were working, it was just the overview that seemed to be broken. I'm wondering if maybe the problem was related to the the Overview page not being able to contact home in order to get the "updates available" information. Is it possible a timeout here was causing the issue?
h
I had this issue too today, after uninstalling the Hibernate extension. Then clicking on overview resulted in the same error. Restart helped
z
yeah we think there's some odd re-deployment mapping caching something to do with inspect never possibly