Tag Info

New answers tagged

0

As Daniel said, you really can't use DNS (domain names) to specify a port; you'd have to have different external IP addresses and then use port mapping on your router to redirect them to different ports. The much better solution, if you're running the web sites on the same machine -- esp. if you're not using SSL (https using older browsers didn't support ...


1

The issue here is that different domains cannot automatically go to different ports. You'd have to type http://admin.example.com:5555, since your browser will automatically try to use port 80. There are some DNS configurations that will decide which website to serve up based on domain name, but they expect you to use port 80 for all of them. If you're ...


0

It conflicts with the sw-nginx package: dpkg: error processing archive /var/cache/apt/archives/nginx-core_1.4.6-1ubuntu3.2_amd64.deb (--unpack): trying to overwrite '/usr/sbin/nginx', which is also in package sw-nginx 1.6.0-1.14060313.ubuntu1404 Remove it: sudo apt-get purge sw-nginx


0

The problem was that the virtual private server only had an IPv6 interface and the location of the official Nginx package does not support IPv6 as of when this question was asked. The hosting company which I use offers IPv6 interfaces for free, and charges extra if you would like an IPv4 interface (since IPv4 addresses are reaching unavailability, it is ...


0

You can check your configuration with sudo nginx -t -c /etc/nginx/nginx.conf Usually that file includes include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; And /etc/nginx/sites-enabled/* are symlinks to /etc/nginx/sites-available/*, so edit the actual files, and check the config before reloading.


1

According to this answer there's an incongruity between the nginx.conf file, and the init script that controls all of the 'service' actions. The line pid /tmp/nginx.pid; should appear in your /etc/nginx/nginx.conf file. This line should be copied into all of the actions within the script at /etc/init.d/nginx wherever there's a reference to pid. Then the ...


0

Try this: sudo kill $(pgrep nginx) if not work try sudo pkill nginx if not work try search for PID of the service: ps aux | grep nginx Then kill by PID: sudo kill -9 PID


0

The eth0 need to be configured as follows netsh interface ip set address name=192.168.0.11 source=192.168.0.1 and assign the eth1 as follows netsh interface ip set address name=”StaticIP” source=dhcp Now restart the network service networking restart Your local application will be available to the local network and it can be tested as follows ...



Top 50 recent answers are included