Hi, Are you logging into chroot before running setup.py? e.g `service gluu-server-4.0 login`

can you please point me to install this release on ubuntu18, sandalone. I did confiure port forwarding file size etc. then did an apt-get install gluu server then fire up the web link on the chrome, i does not work. dont know what is the issue. i can do a fresh install if you provide me where i can follow a simple one page instructions on how to install this. I did successfully install the 3.5 not this puppy

Mohamed, [Here](https://gluu.org/docs/ce/4.0/installation-guide/install-ubuntu/#ubuntu-server-1804x) is the doc.

Hi Fazil, I'd appreciate if you can take a screenshot of steps you have performed and upload it somewhere and share us the link to further troubleshoot. We've been able to install Gluu Server successfully on Ubuntu18.

Hi, Mohamed. I've been able to install 4.0beta in Bionic as well, no issues so far. But that sentence in your original post: >it complains that the oxauth.war file is missing and looking in the directory /opt/dist/gluu/oxauth.war >it should look into the install directory, which is /opt/gluu-server/opt/dist/gluu/oxauth.war looks a bit strange to me. Actually, the path `/opt/dist/gluu/oxauth.war` is correct, as `setup.py` is run from inside the container, so all paths will be relative to its root. The fact that you expect it to be relative to `/opt/gluu-server/` made me wonder whether you actually enter container before running it. Please note that this step - `# /sbin/gluu-serverd-4.0 login` - is mandatory, prior to running the script. If this is not the case and you are able to enter the container, please provide us all log files this command will return: `# ls /install/community-edition-setup/*.log` Also, please follow Sahil's suggestion and share with us a step-by-step of your actions, and the full list of options you select when running `setup.py` (just save all output it displays when you run it).

I would suggest to completely remove the current installation, and start from scratch, following all steps in the guide Zico suggested. Make sure you are inside chroot before running the `setup.py`, then if it won't work, please gather all the data requested so far, and share with us.

Issue was resolved during the call.