Using a Proxy to Access EPEL from an Internal Network

I had some RHEL6 boxes on an internal network that had no access to the internet. But I wanted to install packages from EPEL via yum. The answer was to set up a proxy server and tell these internal boxes to use the proxy. Approach:

  1. Set up Squid proxy on a server that has access to the internet

Solved: iSCSI disconnects and timeouts after successful login

Consider the following from /var/log/messages:

Topic: 

Solved: Apache SSL virtual host says "\x16\x03\x01"

When setting up a second SSL Apache virtual host, you may be frustrated when your browser can't connect and tells you something like

Safari can't establish a secure connection to the server "servername"

In your ssl_request_log you see baffling entries like this:

"\x16\x03\x01" 240
"\x16\x03" 240

This is because you have forgotten to enable SSL for your virtual host with the following:

SSLEngine on

You'll probably need some other SSL-based directives in there, too.

Reference:

Topic: 

Solved: pubcookie access to file failed, reason: verification of user id '<null>' not configured

You've spent hours getting your encryption keys in order. You've successfully got a granting key and a crypt key from your pubcookie server. Your Apache ssl.conf is finely honed and your external SSL tests are flawless.

Yet your users can't log in. They're not being redirected to the central login server. Instead, they see messages like

Topic: 

Pages

Subscribe to SysArchitects RSS