Can you upload the `/opt/gluu/jetty/oxauth/logs/oxauth.log` `/opt/gluu/jetty/identity/logs/oxtrust.log` and also check to see if the Apache log says anything interesting. Are you sure the OpenLDAP server started ok? If not, the logs from above will show it.

In, Shailesh. > I followed this tutorial to install the gluu-server on the ec2 instnce Gluu-server installation (official) Could you please provide a link to the doc page you used? Then please follow Michael's suggestions and provide logs he mentioned using any way you find suitable. I think it would be even better if you'll provide the whole contents of `/opt/gluu/jetty/oxauth/logs/` and `/opt/gluu/jetty/identity/logs/` directories. In addition to logs mentioned above, please also provide next ones: - `/var/log/openldap/ldap.log` - `/etc/httpd/logs/` (whole dir)

when i try ``` /opt/gluu/jetty/oxauth/logs/oxauth.log ``` ``` /opt/gluu/jetty/identity/logs/oxtrust.log ```, it returns me as "no such file and directory". When i navigate to those directory there are only these kind of files.<br> ``` 2017_03_29.stderrout.log 2017_03_29.stderrout.log.201907592 2017_03_29.stderrout.log.153315826 start.log 2017_03_29.stderrout.log.200541052 ``` THese are the all logs files there. and i used this documentation of RHCL 7.2 though I am using RHCL 7.3.[Documentation to install gluu](https://gluu.org/docs/ce/latest/installation-guide/install/)

Please share everything you can then.

Current Directory:**/opt/gluu-server-3.0.1/etc/httpd/logs** Here the result of **cat error_log** ``` [Thu Mar 30 01:13:11.717281 2017] [proxy:error] [pid 1439] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:8082 (localhost) failed [Thu Mar 30 01:13:11.717322 2017] [proxy:error] [pid 1439] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 5s [Thu Mar 30 01:13:11.717331 2017] [proxy_http:error] [pid 1439] [client 71.195.142.112:61566] AH01114: HTTP: failed to make connection to backend: localhost [Thu Mar 30 01:20:19.668656 2017] [proxy:error] [pid 1437] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:8082 (localhost) failed [Thu Mar 30 01:20:19.668695 2017] [proxy:error] [pid 1437] AH00959: ap_proxy_connect_backend disabling worker for (localhost) for 5s [Thu Mar 30 01:20:19.668704 2017] [proxy_http:error] [pid 1437] [client 71.195.142.112:61865] AH01114: HTTP: failed to make connection to backend: localhost ```

Thanks, Shailesh. Please provide us output of next commands: - In container: `# netstat -nlpt` - Outside of container: `# rpm -qi gluu-server-3.0.1` Here is what you should try after that: 1. Please restart all services in the container as explained [here](https://support.gluu.org/installation/3851/connection-refused-http-attempt-to-connect-to-1270018082-localhost-failed/#at20091) 2. Wait for 5-10 minutes and try to access web UI again 3. If issue is still present, please package all contents of `/etc/httpd/logs`, `/opt/gluu/jetty/oxauth/logs/` and `/opt/gluu/jetty/identity/logs/` and share with us using any file sharing service you like.

Please also provide output of `# ps -aux | grep -i java` from the container.

Output of #netstat -nlpt ``` Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:11211 0.0.0.0:* LISTEN 2301/memcached tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd tcp 0 0 172.31.28.48:80 0.0.0.0:* LISTEN 831/httpd tcp 0 0 0.0.0.0:60022 0.0.0.0:* LISTEN 64/sshd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 304/master tcp 0 0 172.31.28.48:443 0.0.0.0:* LISTEN 831/httpd tcp 0 0 127.0.0.1:1636 0.0.0.0:* LISTEN 2330/slapd tcp6 0 0 :::11211 :::* LISTEN 2301/memcached tcp6 0 0 :::111 :::* LISTEN 1/systemd tcp6 0 0 :::60022 :::* LISTEN 64/sshd tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 ::1:25 :::* LISTEN 304/master ``` Output of rpm -qi gluu-server-3.0.1 ``` Name : gluu-server-3.0.1 Version : 2 Release : 1.rhel7 Architecture: x86_64 Install Date: Thu 30 Mar 2017 02:04:48 AM EDT Group : Gluu Size : 1542093528 License : MIT Signature : RSA/SHA256, Fri 03 Mar 2017 03:02:58 PM EST, Key ID 5b76117e0544ba38 Source RPM : gluu-server-3.0.1-2-1.rhel7.src.rpm Build Date : Sun 26 Feb 2017 10:48:15 AM EST Build Host : rhel7-rpm Relocations : (not relocatable) Packager : Gluu support <support@gluu.org> Vendor : Gluu, Inc. Summary : Gluu chroot CE environment Description : Gluu base deployment for CE ``` Output of # ps -aux | grep -i java ``` root 17951 0.0 0.0 112648 976 pts/1 R+ 11:45 0:00 grep --color=auto -i java ``` Output of /etc/httpd/logs/error_log ``` [Thu Mar 30 09:48:55.212579 2017] [proxy:error] [pid 2735] (111)Connection refused: AH00957: HTTP: attempt to connect to 172.31.28.48:8082 (swebtech.info) failed [Thu Mar 30 09:48:55.212608 2017] [proxy:error] [pid 2735] AH00959: ap_proxy_connect_backend disabling worker for (swebtech.info) for 5s [Thu Mar 30 09:48:55.212612 2017] [proxy_http:error] [pid 2735] [client 139.162.116.133:50350] AH01114: HTTP: failed to make connection to backend: swebtech.info, referer: https://52.45.118.60:443/ ``` [http://pasteboard.co/PHyYiEZwI.png](http://pasteboard.co/PHyYiEZwI.png)

Without the oxAuth, oxTrust and LDAP logs, we can't help you.

Michael is correct, please provide everything in log directories mentioned above. So far, from output of those 2 commands, it seems like no Gluu components were started. No running jvms, nothing is listening on backend's ports. Sorry for obvious question, but you did run `./setup.py` when installing the package, right? And did you also disable SElinux at this box?

yes I did `./setup.py`, okay i will put each and every log. I will check everything once again.

Hi, Shailesh. We are closing ticket due to inactivity. You still can post to it in case you'll have something to add.

Please also note that a [similar issue](https://support.gluu.org/installation/3971/gluu-server-503-error) was resolved by adding an extra CPU unit to the VM. Gluu server deployments require VMs with at least 2 CPU units. Also make sure you've met other requirements listed [here](https://gluu.org/docs/ce/3.0.1/installation-guide/)

Hi Niket, As you have seen in other comments; it's hard for us to suggest anything without proper log. 503 might come for various reasons, a famous one is not sufficient resources in your Gluu Server. Throw 8GB memory in your Gluu Server box and allocate memory accordingly in /etc/default/oxauth,identity,idp etc.

Hi, Niket. A couple suggestions here. First of all, you should create a new ticket, this one is pretty old. I would also suggest you in cases when you have that much of lengthy text blocks to share to pack all of them in one archive and host at some free file hosting service out there, sharing link to it on the board.