I have hosted my website as application on IIS and I can access it by http:\localhost\myApp\default.aspx but not with my IP.
Hi guys -
Operating system CentOS Linux 5.5
Kernel and CPU Linux 2.6.18-194.11.3.el5 on x86_64
hosted with sonic.net
we have a strange setup for one of our clients... the problem is that the machine was orginal setup with mysql and php and when they build out the website...
I have 2 websites hosted on an IIS 7 server.
We have a production environment and an UAT environment, the authentication settings on both the servers are the same. Now, when I deploy the application onto the production the application is logging me out with ReturnUrl.
Hi All
I'm trying to create a website using python and wsgi. I've been following instructions such as these.
This works brilliantly as long as I'm accessing the website on the same computer on which it's hosted.
Our main sponsor, eUKhost, now provides Linux Mint with an additional dedicated server.
The server is located in Milton Keynes, UK, and features the following specifications:
E3-1230 Quad Core Intel Xeon CPU (SAS)
8 GB DDR3 RAM
2 x 300 GB SAS 15k rpm RAID 1
3000 GB bandwidth
This £189/month server is provided to Linux Mint for free as part of eUKhost’s sponsorship.
During the release of Lin
i have a webserver on which a website is hosted. server configured with
php version 5.2.6
mysql version 5.0
website is working fine on this server.
now i want to migrate this website to another server which configured with
php version 5.3
mysql version 5.1
the problem is that after migrating the website.
I have a J2EE application hosted on a linux VPS server. I use nginx as the web server and tomcat6 as the application server. At times, the website keeps waiting to load or sometimes even throws a 504 bad gateway nginx error. During this downtime of a few minutes(typically 3-5 minutes), if I try to access the server via SSH, I get a connection timeout error.
I have a CentOS 5.3 server hosting our companies website. The connection to the site is through a Cisco RVS4000 security router. The website is the only device on the network that uses this router and the router only has one inbound rule which forwards port 80 to the website.
I setup the Linux environment following instruction I found here for CentOS 5.3 over a year ago.