Felix Jen's questions

As a bit of a testbench before deployment, I'm running a Supermicro X10DRL-i w/ dual Xeon E5-2620v4's and 64GB RAM. I have a Sapphire AMD Vega56 in the 16x slot.

I was running some stress tests today to check for system stability and I ran into an issue with Furmark on Win10 with the GPU passes through and a slight overclock applied. The system appeared to run fine, but occasionally, the motherboard would make 4 beeps in rapid succession, a similar beep pattern to when doing an IPMI-based reset.

I can't seem to find any errors in either the Windows or IPMI event log and the system appeared otherwise stable, even for those beeps. Turning off the Furmark stress test stopped those beeps from happening, but it seems weird that it could even cause something like that.

Anyone have any insight?

I have a strange scenario where I have 2 OpenVPN servers on my LAN (192.168.1.0/24) both over TUN. Server A (on 192.168.1.100) provides clients with addresses on the 172.16.0.0/24 subnet and Server B (192.168.1.1) provides clients with the 172.16.10/24 subnet.

Clients on the 2 OpenVPN Servers need to talk to each other. I've applied the following config to Server A:

push "route 172.16.1.0 255.255.255.0 192.168.1.1 1"

The resulting routing table entry for a client on Server A is:

172.16.1/24 192.168.1.1 UGSc 0 2 en0

On server B, I applied the config:

push "route 172.16.0.0 255.255.255.0 192.168.1.100 1"

On both servers, I made sure to allow access to the both the LAN and the other OpenVPN's networks. However, attempting to ping 172.16.1.1 on a client connected to Server A, results in "Network Unreachable." The similar occurs with a client on Server B.

If it is of any additional use, Server B resides on Pfsense. Server A is a virtualized OpenVPN Access Server.

I have just configured a Microsoft Remote Desktop Services service on an internal Windows Server 2012 R2 server. I have access to RDP through outside the network with port forwarding. However, because I have additional web servers running on port 80/443, I can't expose RD Web Access running on IIS to directly to the internet.

I have a reverse proxy configuration with Apache for all my internal sites, so I'm trying to use the same for RD Web Access. My configuration (for both HTTP & HTTPS) is as follows

<VirtualHost *:80>
    ServerName foo.example.com

    ProxyPass / http://192.168.1.xxx/
    ProxyPassReverse / http://192.168.1.xxx/
</VirtualHost>

This configuration seems to work but has an issue. When connecting directly to foo.example.com, I get the default IIS page, as expected. However, when accessing http://foo.example.com/RDWeb/, the URL gets changed to http://192.168.1.xxx/RDWeb, which I obviously can't access from outside of my network. I need it to stay as http://foo.example.com/RDWeb/.

I have tried adding ProxyPreserveHost On to my apache configuration, when I do that, I get an infinite redirect loop, so that doesn't work either. I'm pretty sure that this is NOT an IIS issue, because if I set my local host file to point foo.example.com to 192.168.1.xxx, it works without issue.

Is there something I'm missing in my Apache Reverse Proxy configurations?

I've been trying to get fail2ban to work with the Xeams email spam filter. But, I can't figure out what possible regex I should use to match the logs. The logs are in this format.

61.240.144.65   1451702136946   5
185.130.5.240   1451702444872   5
192.237.159.38  1451705774912   5
185.130.5.240   1451712868825   5

Each section of the log is separated by a Tab (I think), with the first part being the host IP. I have no idea what the other sections do.

I've tried the following regex but it doesn't work according to fail2ban-regex.

<HOST>      1451.*  .*

As well as:

<HOST>      .*  .*

I honestly have no idea what to do to match these logs.

I just ran SMART on my server's drives but I'm not too sure how to interpret it.

My results seem like the drive is doing fine, but I would like a second (or third) opinion, just to be safe.

Here are the results:

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   120   099   006    Pre-fail  Always       -       243846539
  3 Spin_Up_Time            0x0003   097   097   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       1007
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000f   077   060   030    Pre-fail  Always       -       57855713
  9 Power_On_Hours          0x0032   074   074   000    Old_age   Always       -       22900
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       521
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   067   052   045    Old_age   Always       -       33 (Min/Max 28/37)
194 Temperature_Celsius     0x0022   033   048   000    Old_age   Always       -       33 (0 15 0 0 0)
195 Hardware_ECC_Recovered  0x001a   035   014   000    Old_age   Always       -       243846539
197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       14491219680816
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       2006043213
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       4019475959

I am running an Ubuntu 14.04 LTS server with Apache installed. I have 3 Virtual Hosts set up, with another Default Server to catch all other requests not taken care of. The Default Server has a Document Root of /var/www/. The other 3 Virtual Hosts have a Document root of /var/www/html/.../.

I have all three Virtual Hosts enabled on their respective Domain Names that are only available for local access at this point for testing. However, whenever I try to access one of the three Virtual Hosts, I get instantly booted to the Document Root of the Default Server.

This is the config of one of the Virtual Hosts, with the other ones being pretty much the same, except some fields which obviously must be changed (Doc Root, Server Name). I have replaced the Server Name and the Document Roots, but both are legitimate and exist on the server, if that matters.

<VirtualHost [example.com]>
DocumentRoot "/var/www/html/[Directory]“
<Directory "/var/www/html/[Directory]“>
    allow from all
    Options None
    Require all granted
</Directory> 
ServerName [example.com] 
</VirtualHost>

This is the default-ssl.conf file.

<IfModule mod_ssl.c>
<VirtualHost _default_:443>
    ServerAdmin webmaster@localhost

    DocumentRoot /var/www/html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

    #   SSL Engine Switch:
    #   Enable/Disable SSL for this virtual host.
    SSLEngine on

    #   A self-signed (snakeoil) certificate can be created by installing
    #   the ssl-cert package. See
    #   /usr/share/doc/apache2/README.Debian.gz for more info.
    #   If both key and certificate are stored in the same file, only the
    #   SSLCertificateFile directive is needed.
    SSLCertificateFile  /etc/ssl/certs/ssl-cert-snakeoil.pem
    SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key

    #   Server Certificate Chain:
    #   Point SSLCertificateChainFile at a file containing the
    #   concatenation of PEM encoded CA certificates which form the
    #   certificate chain for the server certificate. Alternatively
    #   the referenced file can be the same as SSLCertificateFile
    #   when the CA certificates are directly appended to the server
    #   certificate for convinience.
    #SSLCertificateChainFile /etc/apache2/ssl.crt/server-ca.crt

    #   Certificate Authority (CA):
    #   Set the CA certificate verification path where to find CA
    #   certificates for client authentication or alternatively one
    #   huge file containing all of them (file must be PEM encoded)
    #   Note: Inside SSLCACertificatePath you need hash symlinks
    #        to point to the certificate files. Use the provided
    #        Makefile to update the hash symlinks after changes.
    #SSLCACertificatePath /etc/ssl/certs/
    #SSLCACertificateFile /etc/apache2/ssl.crt/ca-bundle.crt

    #   Certificate Revocation Lists (CRL):
    #   Set the CA revocation path where to find CA CRLs for client
    #   authentication or alternatively one huge file containing all
    #   of them (file must be PEM encoded)
    #   Note: Inside SSLCARevocationPath you need hash symlinks
    #        to point to the certificate files. Use the provided
    #        Makefile to update the hash symlinks after changes.
    #SSLCARevocationPath /etc/apache2/ssl.crl/
    #SSLCARevocationFile /etc/apache2/ssl.crl/ca-bundle.crl

    #   Client Authentication (Type):
    #   Client certificate verification type and depth.  Types are
    #   none, optional, require and optional_no_ca.  Depth is a
    #   number which specifies how deeply to verify the certificate
    #   issuer chain before deciding the certificate is not valid.
    #SSLVerifyClient require
    #SSLVerifyDepth  10

    #   SSL Engine Options:
    #   Set various options for the SSL engine.
    #   o FakeBasicAuth:
    #    Translate the client X.509 into a Basic Authorisation.  This means that
    #    the standard Auth/DBMAuth methods can be used for access control.  The
    #    user name is the `one line' version of the client's X.509 certificate.
    #    Note that no password is obtained from the user. Every entry in the user
    #    file needs this password: `xxj31ZMTZzkVA'.
    #   o ExportCertData:
    #    This exports two additional environment variables: SSL_CLIENT_CERT and
    #    SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
    #    server (always existing) and the client (only existing when client
    #    authentication is used). This can be used to import the certificates
    #    into CGI scripts.
    #   o StdEnvVars:
    #    This exports the standard SSL/TLS related `SSL_*' environment variables.
    #    Per default this exportation is switched off for performance reasons,
    #    because the extraction step is an expensive operation and is usually
    #    useless for serving static content. So one usually enables the
    #    exportation for CGI and SSI requests only.
    #   o OptRenegotiate:
    #    This enables optimized SSL connection renegotiation handling when SSL
    #    directives are used in per-directory context.
    #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
            SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory /usr/lib/cgi-bin>
            SSLOptions +StdEnvVars
    </Directory>

    #   SSL Protocol Adjustments:
    #   The safe and default but still SSL/TLS standard compliant shutdown
    #   approach is that mod_ssl sends the close notify alert but doesn't wait for
    #   the close notify alert from client. When you need a different shutdown
    #   approach you can use one of the following variables:
    #   o ssl-unclean-shutdown:
    #    This forces an unclean shutdown when the connection is closed, i.e. no
    #    SSL close notify alert is send or allowed to received.  This violates
    #    the SSL/TLS standard but is needed for some brain-dead browsers. Use
    #    this when you receive I/O errors because of the standard approach where
    #    mod_ssl sends the close notify alert.
    #   o ssl-accurate-shutdown:
    #    This forces an accurate shutdown when the connection is closed, i.e. a
    #    SSL close notify alert is send and mod_ssl waits for the close notify
    #    alert of the client. This is 100% SSL/TLS standard compliant, but in
    #    practice often causes hanging connections with brain-dead browsers. Use
    #    this only for browsers where you know that their SSL implementation
    #    works correctly.
    #   Notice: Most problems of broken clients are also related to the HTTP
    #   keep-alive facility, so you usually additionally want to disable
    #   keep-alive for those clients, too. Use variable "nokeepalive" for this.
    #   Similarly, one has to force some clients to use HTTP/1.0 to workaround
    #   their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and
    #   "force-response-1.0" for this.
    BrowserMatch "MSIE [2-6]" \
            nokeepalive ssl-unclean-shutdown \
            downgrade-1.0 force-response-1.0
    # MSIE 7 and newer should be able to use keepalive
    BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

</VirtualHost>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

This is the 000-default.conf. I don't know why nothing is showing on it other than this line.

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

How do I get the Virtual Hosts to display the correct directory when accessed? If it makes any difference, I'm administrating the Apache Server over Webmin 1.750 on Ubuntu Server 14.04 LTS

I have read somewhere that I need to specify a Server Name for the Default Server, or else it will catch all requests since it is the very first server on the list. Is this true? If so, how do I do so?

I am hosting multiple websites on an instance of OS X Server 4.0 with an issue. I have a default personal site that is available on the normal domain and the www subdomain. I tried to configure other sites to have that similar result also. However, I am running into a problem. My virtual hosts (other sites) have the www subdomain configured in the DNS records. I configured my Virtual Hosts in OS X Server with 0 additional domains, redirects, or aliases. All other settings are also left default.

The DNS on OS X Server is configured correctly as well. When I try to access http://example.com/ it sends me to the Virtual Host correctly. However, when I do http://www.example.com/ it sends me to the Server Default website, which is my personal site. The only way I can fix this is to add another website using the www.example.com into the list.

Is there another way to fix this instead of adding another site to the list?