spawning multiple connections to port 80 when accessing from the ip - ruby-on-rails-3

I have a rails app which is hosted in a shared server. last few days I have been experiencing a slowness in the site.
When I contacted the hosting support, they said, It seems that each time when we access the domain it's spawning 20 connections to port 80
what are the possibilities of being such thing.
could it be a network setup issue
could it be a rails config isssue
anyhelp would be appreciated, thanks
my site runs on
Rails 3.2.9
Passenger

It sounds like a programming error in the client, unless your server creates self-connections, in which case the server end needs attention.

Related

Weblogic 10.3.6 managed server fails to start when unsecured listen port is disabled

This server worked not too long ago (I don't have a specific date). We use it for testing and had successfully deployed a few applications. Upon returning to the project I could no longer access the applications chrome saying the site cannot be reached when I netstat -an | grep 'LISTEN'.
I can see the unsecured port but the SSL port is missing in action. I asked the networking team if the ports were being blocked and they said no. I tried to force the application to use the secure port by disabling the unsecured port, restarting the managed server but the it fails to start with this configuration.
Any thoughts? SSL is not really my area of expertise (this is my first exposure). When googling the title I didn't see any results that matched the problem I am having, or at least I did not realize they did...
The server will restart if I enable the unsecured port.
# Gerardo Arroyo, yes this seems to be the issue. I assumed that this server used the same certs as other servers in the test system but it seems I was wrong. I will request a new cert from the networking team. Thank you

yii 1.1.16 application needs VPS not shared hosting, is that true?

I have a Yii 1.1.16 application previously developed by someone else.
I tried to host it on a shared environment (FatCow) but it produces several SMTP errors. I have spent multiple hours of my time reading remarks about this subject here, but no hope. The guy who developed it said this application should be hosted on VPS or a dedicated server or it will not work at all.
How true this is (it will not work on Shared host and it will work on VPS)?
The error: smtp error could not connect to smtp host
The SMTP is working fine outside the app.
Thank you in advance.
Luai
Yii 1.1.16 is nohow limited to VPS. You can host it anywhere where you meed requirements.
It could be two possible issues:
The application requires some specific SMPT configuration that is not provided by most shared hosts
The application need to be reconfigured to use the SMTP setup from shared hosting where it is hosted
#Zmilan was right.
After long days of hard work, SMTP and email are working fine.
I also found out that the application can work fine on shared hosting, but because it requires the Redis server and Redis PHP extension I had to move to VPS for further installations.

Apache/IIS relay

In my LAN I have two web servers, one Apache Linux Server (Debian) and one Microsoft Web Server (IIS7).
Apache has three webpages, i.e., apache01.com apache02.com and apache03.com and IIS7 has microsoft01.com and microsoft02.com
My question is:
To access from outside LAN to any domain, what is better? NAT port 80 to IIS7 or to Apache?
And then, How to delay from Apache/IIS7 to IIS7/Apache the domains it doesn't manage?
I've never done this, so I ask because it could be a lot of thinks I'm not seeing.
I don't need a full procedure, only a guidelines to continue researching.
Thanks
The solution, here
The key is IIS URL Rewrite Module and Reverse proxy

Serving two sites (Apache and Node.JS) from one server

I am on Dreamhost VPS with root access. It runs Apache, and is hosting a site "www.example.com". At the same time, I am developing a Node.js web site, and binding Node.js to port 3456 (for example). So the Node.js site is accessible by typing "www.example.com:3456".
These are two distinct websites. I don't ever want users of the "www.example.com" accessing my Node.js website (which will be migrated to Nodejitsu after development).
Will I run into any problems with this setup?
I do not believe this will be a problem, unless one of your visitors happens to end up at port 3456. To mitigate this, you should think about writing your own small piece of middleware to whitelist your IP (thus rejecting anyone else). You can see an example at: http://www.hacksparrow.com/how-to-write-midddleware-for-connect-express-js.html. I'm sure you wont have a problem modifying this to your needs.

Redirecting web traffic in a server hosting both an Apache and a Glassfish web

I am hosting two web pages in my server. One is running on Apache and the another one on Glassfish. By now I solve the redirection problem making the Glassfish server to listen on a port distinct than the 80. The problem is that I think my web users have a firewall blocking those ports so they canĀ“t access the GlassFish web. Which way would you recommend me to take in order to make a URL request-based redirection? I want to make the glassfish web a subdomain of the Apache one, being both running at the same IP.
If I have not been sufficiently clear with my question, please let me know
Thank you for your time.
Have you tried modifying the domain or using subdomains? If one application is eg. at http://subdomain1.yourdomain.net and another at http://subdomain2.yourdomain.net it should do the trick without any problems. Or try http://yourdomain.net for your main program and http://yourdomain.net/somecontext for sub program. That looks meaningful also for the service user.
Tick the answer if you got help :)