Saturday, August 26, 2017

GWT Application gets “404 The requested resource is not available”.

Hi there.


I do not know why I keep getting "404 The requested resource is not available", when I am accessing my GWT Application. I am hosting my GWT application, on my TomEE/8.5.6 (7.0.2) at home, currently.

Here is the situation.

  1. I am able to use my GWT application from "TomEE Web Application Manager" as (http)://192.168.1.70:8080/Index

  2. However, when I type (http)://www.zethanath.tk in the browser, I would get (https)://www.zethanath.tk/ with HTTP Status 404.

Here is the details of my configuration.


Ubuntu:/opt/tomcat/webapps$ ls -l  total 20932  drwxrwxr-x 14 tomcat tomcat     4096 Aug  4 11:46 docs  drwxrwxr-x  5 tomcat tomcat     4096 Aug  4 11:46 host-manager  drwxrwxrwx  5 tomcat tomcat     4096 Aug 25 08:46 Index  -rwxrwxrwx  1 tomcat tomcat 21411520 Aug 25 08:46 Index.war  drwxrwxr-x  5 tomcat tomcat     4096 Aug  4 11:46 manager  drwxrwxr-x  3 tomcat tomcat     4096 Aug  8 17:30 ROOT

sudo nano 000-default.conf

<VirtualHost *:80 > Protocols h2 http/1.1 ServerAdmin erick9.hi5@gmail.com ServerName www.zethanath.tk ServerAlias servlet.zethanath.tk zethanath.tk DocumentRoot "/opt/tomcat/webapps/Index" ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined RewriteEngine on RewriteCond %{SERVER_NAME} =www.zethanath.tk RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] </VirtualHost> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

sudo nano default-ssl.conf

<IfModule mod_ssl.c> <VirtualHost _default_:443> Protocols h2 http/1.1 ServerAdmin erick9.hi5@gmail.com ServerName www.zethanath.tk ServerAlias servlet.zethanath.tk zethanath.tk DocumentRoot "/opt/tomcat/webapps/Index" JKMountCopy On JKMount /* ajp13_worker ErrorLog ${APACHE_LOG_DIR}/error.log CustomLog ${APACHE_LOG_DIR}/access.log combined SSLEngine on SSLCertificateFile /etc/letsencrypt/live/zethanath.tk/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/zethanath.tk/privkey.pem Include /etc/letsencrypt/options-ssl-apache.conf <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory /usr/lib/cgi-bin> SSLOptions +StdEnvVars </Directory> </VirtualHost> </IfModule> # vim: syntax=apache ts=4 sw=4 sts=4 sr noet

I keep thinking that I need to associate port 8080 with "DocumentRoot "/opt/tomcat/webapps/Index", but I am unsure how.

Here is the details of my UFW. I have similar setup in the router.


sudo ufw status  Status: active    To                         Action      From  --                         ------      ----  OpenSSH                    ALLOW       Anywhere                    Apache Full                ALLOW       Anywhere                    20/tcp                     ALLOW       Anywhere                    21/tcp                     ALLOW       Anywhere                    990/tcp                    ALLOW       Anywhere                    40000:50000/tcp            ALLOW       Anywhere                    Apache Secure              ALLOW       Anywhere                    8080                       ALLOW       Anywhere                    OpenSSH (v6)               ALLOW       Anywhere (v6)               Apache Full (v6)           ALLOW       Anywhere (v6)               20/tcp (v6)                ALLOW       Anywhere (v6)               21/tcp (v6)                ALLOW       Anywhere (v6)               990/tcp (v6)               ALLOW       Anywhere (v6)               40000:50000/tcp (v6)       ALLOW       Anywhere (v6)               Apache Secure (v6)         ALLOW       Anywhere (v6)               8080 (v6)                  ALLOW       Anywhere (v6) 

Help is greatly appreciated.


--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment