Dan Dascalescu's questions

What causes for the delay in connecting to an Nginx server and for the Waiting time are under an admin's control?

I've set up GTMetrix to run daily web page load speed tests, and sometimes I get surprisingly high values for fetching static files. Here's one report:

The GTMetrix analysis occurred 20 minutes ago. Our 1GB Linode web server is far from loaded. Load average: 0.17 0.06 0.06 right now, CPU utilization under 1% around the 5-minute interval during the analysis, nginx connections under 1 per second.

The nginx config file is nothing special, and hasn't changed in weeks:

server {
    listen 80;
    listen [::]:80;
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name analytics.idorecall.com;

    ssl_certificate ...;
    ssl_certificate_key ...;

    root /var/www/piwik;

    location / {
        index index.php;
    }

    location ~* \.(ico|css|js|gif|png|jpe?g)$ {
        add_header Access-Control-Allow-Origin idorecall.com;
        access_log off;
        expires max;
        break;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;

        fastcgi_pass unix:/var/run/php5-fpm.sock;
    }
}

On the other hand, Google's Tag Manager .js also took 2 seconds to download, so maybe the problem is on GTMetrix's side? Are these random slow load times worth investigating, or should I chalk them off as a connectivity vagaries?

We run a social/local service that benefits from geolocating the IP of users. The problem is that with IPv6, geolocation is quite a bit spottier than with IPv4.

Is there a way to prefer incoming connections over IPv6, on a Ubuntu host with nginx? The config looks like this:

server {
    listen 80 default_server;
    listen [::]:80 ipv6only=off default_server;
}

I've posted this question on WP.SE, but got no replies. In the meantime I figured a solution involving proxy_pass, but it comes with a few downsides.

I have a subdomain installation of Wordpress that I'd like to serve instead at /blog. This must be an FAQ, but I haven't nailed the search terms for it (/blog being so common doesn't help).

Where can I find a full nginx config file and wp-config settings that have WordPress live at /blog? Do I need to alter any WP settings in its MySQL database? Is it practical to move my existing instance, or should I start from scratch?

I have a very basic nginx setup that redirects www.example.com to example.com, following the best practice. It works, and in the Tor Firefox browser, going to http://www.idorecall.com/blog indeed updates the URL in the address bar to http://idorecall.com/blog.

But this doesn't change the URL in the address bar of Chrome, Firefox Portable, IE and Opera Portable.

Here's the modified default nginx config. There are no other nginx config files other than nginx.conf.

server {
  server_name www.idorecall.com;
  return 301 $scheme://idorecall.com$request_uri;
}

server {
    listen 80 default_server;
    listen [::]:80 default_server;

    root /var/www/html;

    index index.html index.htm index.nginx-debian.html;

    server_name idorecall.com;

    location / {
        try_files $uri $uri/ =404;
    }

    location /blog {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header HOST $http_host;

        proxy_pass http://127.0.0.1:2368;
    }
}

wget -S, http://www.rexswain.com/httpview.html, browsershots etc. correctly detect the 301 "Moved permanently" redirect. Most browsers though preserve the www URL. Super frustrating. Firefox and Opera were installed from scratch, so there's no history hit of the www domain.

GitHub manages to redirect http(s)://www.github.com to https://github.com in every browser. How do they do this?

I've read the instructions on installing older versions but it appears that 2.4 is no longer available in the repos?

aptitude -y install mongodb-org-server=2.4
Unable to find a version "2.4" for the package "mongodb-org-server"
Unable to find a version "2.4" for the package "mongodb-org-server"
The following NEW packages will be installed:
  mongodb-org-server
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/9,416 kB of archives. After unpacking 23.7 MB will be used.
Selecting previously unselected package mongodb-org-server.
(Reading database ... 33931 files and directories currently installed.)
Preparing to unpack .../mongodb-org-server_2.6.3_amd64.deb ...
Unpacking mongodb-org-server (2.6.3) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up mongodb-org-server (2.6.3) ...
mongod start/running, process 30690

UPDATE: I've also filed a ticket with Mongo's JIRA, which has received a reply.

A white paper published by Diskeeper Corporation states at page 3 that,

The most common problems caused by file fragmentation are:

a) Crashes and system hangs/freezes
b) Slow boot up and computers that won't boot up
c) [...]
d) File corruption and data loss
e) Errors in programs
f) RAM use and cache problems

How accurate are these statements (especially the ones about crashes and aborted bootups)?