I am trying to login to Lucee admin on an EC2 server. Lucee appears to be running fine - it is serving pages for the website(s) that use it. It is currently on version 5.3.9.141. When admin login page loads and I enter the password it loads the admin but the message: 'Error, requested action doesn't exist' appears on the main content section. Clicking on any of the menu items returns to login. I have read the changelog for Lucee and can see that this has possibly been fixed in a more recent version however, I cannot get into the admin to do the update. I have read that I can drop an updated lco file into the

{server-context}/patches

folder but I can't seem to locate this on our server. Lucee is install using the standard Lucee installer for ubuntu so I have the following location:

/opt/lucee

. I then have the following items in that folder: install.log jre jre.bak lib lucee.ico lucee_ctl mod_cfml sys tomcat tomcat.ico uninstall uninstall.dat If I look inside

tomcat

I can see a

lucee-server

folder but would need to chown/chmod permission in order to get into it. Is this what I need to do? Will I then find the patches folder in there?

I don't know the answer here, but something to consider is using CommandBox to run your Lucee websites instead of installing Lucee natively. There are several advantages to this including the ability to easily specify the Lucee version the site runs on as well as use cfconfig to manage the server config.

This is a known issue

@bdw429s yes, I did find the issue on the JIRA. Hence why I am asking how to update to the latest 5.x version. I can do the usual update from within Lucee Admin due to the error/login cycle. The question is really about where I need to upload the updated lco file on an Ubuntu install. Lucee appears to be installed to

/opt/lucee/

which contains a

tomcat

folder which has a

lucee-server

folder within it. Currently this has lucee as the owner and group and therefore I would need to change this in order to get into it to be able to find the server-context/patches folder. Just really asking if that is the best/only way to do it? @garciadev Commandbox on a prod server isn't something we have looked into yet but it certainly would make life easier - we use commandbox in dev everyday!

@davla I can highly recommend looking into that. 🙂 We have many clients that are using CommandBox in production which makes managing their environments and configuration much easier. You can either use CommandBox as your main webserver or you can reverse proxy to it if you need a more complicated setup.

@garciadev Sounds like something to look into - any docs on the reverse proxy aspect? We are currently using Apache as our webserver and sites are configured with conf and htaccess files etc so would be good to only change one thing - can always migrate away from Apache at a later date.

Reverse proxy is pretty straightforward. I use it with NGINX but it should work the same. Set up CommandBox to run on whatever port you specify, then specify that URL in the webserver config. For Apache, it will be the same reverse proxy setup for any server.

The easiest way to update is to grab the latest Lucee jar and just overwrite your current one