I have two issues:
When I first started Elastic BeanStalk it had Apache webserver for Java8 Tomcat8 combination.
I was able to access my webapp using the link shown
a) https://i.stack.imgur.com/PmEka.png
After working on Apache, I went to configurations and changed the server to
nginx as I would like to try nginx.
I re-deployed and restarted app server after changing my webserver to nginx in my configuration, and
Issue 1: not able to access homepage by clicking link (as shown in a) )
Issue 2: The webpage title still shows as "Apache..." Why is that?
https://i.stack.imgur.com/l17WJ.png
But when I checked chrome console, I see nginx there.
Tomcat is an Apache Software Foundation project. Your screenshot is of an "Apache Tomcat" error page. It is not telling you that the Elastic Beanstalk reverse-proxy is Apache Web Server, it is simply telling you that the application server is Apache Tomcat.
Related
In Ignite web console document page, it only provides Apache HTTP server conf for the web console in production mode, but I want to know how to configure it via nginx?
Added documentation for Nginx HTTP server configuration. Can you please try?
I'm trying to use my aws certificate with elastic load balancer on my EC2 instance which has Apache. I followed this tutorial http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-getting-started.html#configure-health-check to create my classic load balancer.After that creation everything looks right in my load balancer console . But when i try to browse my website with https instead of http chrome says connection is not secure. When i look inside of certificate from browser i see that certificate published by localhost.
So is there any additional configuration that i have to do like in my httpd-ssl.conf file or something else? By the way all this services are in the same region.(Frankfurt)
Thanks George!!! Route DNS to ELB is the key point. Since you sent that comment i had been working on it. Now i got it! Here is the link of routing DNS to ELB;
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
We have an apache web server through which we redirect requests to Weblogic App server.
Now in case the application on the weblogic server is down, the Apache Web server should detect it and redirect to a static html page(something like saying - application is unavailable currently, instead of showing 404 error).
Can someone please help how this can be implemented ?
Try using the ErrorPage directive within the plugin configuration. When apache is unable to connect to Weblogic, you can redirct to a customer error page located somewhere on apache itself.
The documentation is here
I have been trying to setup an Apache web server along with a Tomcat6 web server, using SSL/HTTPS. On my Apache web server the SSL is working correctly, and I can access the web pages it serves up using SSL/HTTPS, but I am having a problem accessing the web apps on the Tomcat server using SSL/HTTPS. The new setup is on a Centos 6 machine, and I have a similar setup on a Fedora 13 machine.
I have compared all the files that I can think of between the two machines, but can not get to the web apps using HTTPS. When I try I get a "Not Found" error. I can access the web apps if I use just HTTP.
Can anyone point me to where my problem might be?
Thank you
We have a Glassfish running behind an Apache Webserver. Direct requests to the application server are blocked by the firewall. So we have the webserver forwarding requests to the app server via mod_jk. This all works fine for the web apps deployed on x80 ports of Glassfish. But am now left wondering, how do I access the Admin Console GUI? I can do most of the Admin Console things using asadmin, but it'd be good to have the GUI as well.
Thanks!
Nirav
Why not create a new VirtualHost or an Alias which will map to the Glassfish admin console?