Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
mydomain.com is running with nginx1.2, php-fpm, apc on an Ubuntu server (medium - amazon EC2). I have been tweaking my server for past 6 months, however a problem started occurring since the day before yesterday.
I am unable to resolve the root for www.mydomain.com, or mydomain.com. It takes 3 minutes to receive a broken page with all the links on the page converted to the local IP (10.x.x.x). However, any other URL, www.mydomain.com/a, or mydomain.com/a, or www.mydomain.com/a.php etc. resolve perfectly and with the characteristic nginx speed (I am a big fan!). Even www.mydomain.com/index.php resolves perfectly that is basically the same server root i.e www.mydomain.com. So, it seems that requests can not be resolved only if passed without any URL at the end.
I came up with the following three possibilities why this could be happening:
Incorrect host setup: I might be passing incorrect host information in some setting i.e in php-fpm.conf, php.ini, or nginx.conf or in ubuntu under hosts, or hostname.conf etc.
Incorrect index setup: I might be passing incorrect index types in nginx.conf or php-fpm.conf
anything is possible :(
Most importantly, this problem goes away, if I stop using the "server_name" directive in nginx.conf. So, an un-named nginx server block leads to normal operation, but the moment I put in the server_name directive to www.mydomain.com or mydomain.com, then again the domain root becomes unreachable.
This has been driving me crazy for the past two days. Ceaseless googling has been of little help, as it is probably a configuration mis-directive. I humbly bend down, before my computer overlords! Please help!
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I have a website running on wordpress (Bitnami).the server is on an AWS behind an elastic load balancer. However, when i hit the wordpress website, it is taking too long to respond.
There is another nodejs API that is running on the same AWS server (on port 4000). That is returning a response pretty fast. So, this would not be a DNS resoulution issue.
Any idea how i can debug the reason why the wordpress website is taking too long to load?
This will likely be a security group issue judging on the behaviour you're experiencing.
Ensure the following:
The Load Balancers security group allows inbound access (port 80 for HTTP, port 443 for HTTPS)
The instances security group allows inbound access from the load balancer (on the port the application should be loaded from).
Check the health of the host in the load balancer interface within the console.
If the database is external to the instance host (i.e. another server or RDS) then ensure it supports inbound access from the instance (port 3306 for MySQL).
If the database is running on the same server (the default for bitnami) ensure it is connecting to the host as localhost.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I was learning nginx and as I found out that it is a load balancer helping to handle a loads of requests to a server. The question I wanted to ask is that as I also found out, nginx is best to be used when one server gets overloaded and we need to add up one more server. So, is it true that nginx is best to used ONLY when one server cannot handle the number of requests?
Although it looks like Nginx should be added only when you need to load balance between multiple servers, and IMO this decision is correct as sometimes it is good to avoid increasing the entropy if you can't manage it.
But apart from being a load balancer, Nginx is also widely used for:
Reverse proxy for multiple services [virtual hosts] (load balancing isn't mandatory)
Content caching (to avoid request hitting upstream servers everytime)
SSL termination
API Gateway (for security, rate limiting and routing)
Sometimes, also as a web server
so even if you aren't load-balancing you can get benefit from facilities provided by nginx like content caching, SSL termination, rate limiting, etc.
Later when need arises you can easily add more machines in the upstream to start load balancing.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I am trying to find website with url https://example.com:8888 in iis, but iis bindings looks like this, this iis is on a vm instance hosted on azure,
when I do netstat I get this (copied picture from internet but I am getting exact same response for 8888),
Problem:
Wildcard certificate expired on "*.example.com" we renewed it on website in iis, it shows certificate valid for 443(https) and 80(http) but it shows certificate as expired for port 8888. I am unable to find binding for this website with port 8888 so that IT team could update it's certificate.
We stopped IIS server and website on 443 and 80 stoped serving however on port 8888 it kept showing certificate expired and didn't go down. However when we shutdown the server instance, it went down as well.
How to find this website so that we could update it's certificate ? thanks
You could check whether 8888 is listened by (PID 4)IIS by using command line:
netstat -ano
If the command line show that IIS is listening to 8888, then you could use this to find the binding& site with port 8888
appcmd list site
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 12 months ago.
Improve this question
My website has implemented by using JAVA. So we have taken VPS and installed Tomcat then deployed
My website is appearing like this
whenever I click www.mysite.com in url ... it is appearing as below.
http://mysite.com:8080/foldername/
But I would like to see my website as www.mysite.com
Can any one suggest me what to do .. should I do any changes in htaccess file ?
If you don't provide the port number in the URL your HTTP requests would be sent to port 80. You can set up a firewall rule to redirect requests headed towards port 80 to 8080.
If you don't want a port number in your URL, you have to use the default port number for HTTP, which is 80. If it's anything other than 80, you will be required to put the port number in the URL. That's all there is to it.
Now, if your question is "how do I host my Tomcat website on port 80", well there are plenty of answers to that question both on SA and teh intertubes. Just search.
If you wish to redirect all request on tomcat on default port you have to stop the IIS and use port 80 for your tomcat application or make the changes in IIS to redirect it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a good experience with Unicorn configuration with conjunction of Nginx, it works really well after optimizations and tuning procedures. But now I have got a question what is the best way to spread the load across multiple machines with Unicorns.
The question is you have 3 machines (Nginx load balancer, 2 APP servers with Unicorns), how do you manage load balancing of Unicorns with serving static assets.
Do you now any drawbacks with connection to Unicorn over TCP (timeouts, connection lost), is there any other way to upstream socket connection over the network (maybe port forwarding over SSH)? Unicorn designed to be stateless, but how do you manage the edge cases?
I don't want to serve static from balancer node, so would it be ok to setup Nginx on each of APP server and setup dumb Nginx balancer in front of them?
P.S. My current configuration is well-tested and can be found on Github, but the setup with Nginx+Unicorn on the same machine that already became a bottleneck.
UPDATE: Development is rigidly depends on the specific server configuration. Bottlenecks are going to happen not just because of developer's decisions, but also with the environment where he run it. Stackoverlow is full with highly marked Q&A related to the hard-to-know details about specific configuration. Alex who answered below works with Github I'm really appreciate to have a reply by such qualified person!
Don't access the Unicorns over TCP/network.
Your setup seems just fine, you can simply add a load-balancer in front of the APP servers, but I would suggest Keepalived (LVS ftw) as load-balancer instead of Nginx.
You can have them balance connections to the APP servers running Nginx+Unicorns over sockets.