Visit Our UNIX and Linux User Community

Special Forums IP Networking Proxy Server Httpd proxy on AIX: failed to connect SSL Post 303042275 by Neo on Friday 20th of December 2019 04:10:01 AM
Old 12-20-2019
Description:	Controls the verbosity of the ErrorLog
Syntax:	LogLevel [module:]level [module:level] ...
Default:	LogLevel warn
Context:	server config, virtual host, directory
Status:	Core
Module:	core
Compatibility:	Per-module and per-directory configuration is available in Apache HTTP Server 2.3.6 and later
LogLevel adjusts the verbosity of the messages recorded in the error logs (see ErrorLog directive). 

The following levels are available, in order of decreasing significance:

Level	Description	Example
emerg	Emergencies - system is unusable.	"Child cannot open lock file. Exiting"
alert	Action must be taken immediately.	"getpwuid: couldn't determine user name from uid"
crit	Critical Conditions.	"socket: Failed to get a socket, exiting child"
error	Error conditions.	"Premature end of script headers"
warn	Warning conditions.	"child process 1234 did not exit, sending another SIGHUP"
notice	Normal but significant condition.	"httpd: caught SIGBUS, attempting to dump core in ..."
info	Informational.	"Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..."
debug	Debug-level messages	"Opening config file ..."
trace1	Trace messages	"proxy: FTP: control connection complete"
trace2	Trace messages	"proxy: CONNECT: sending the CONNECT request to the remote proxy"
trace3	Trace messages	"openssl: Handshake: start"
trace4	Trace messages	"read from buffered SSL brigade, mode 0, 17 bytes"
trace5	Trace messages	"map lookup FAILED: map=rewritemap key=keyname"
trace6	Trace messages	"cache lookup FAILED, forcing new map lookup"
trace7	Trace messages, dumping large amounts of data	"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"
trace8	Trace messages, dumping large amounts of data	"| 0000: 02 23 44 30 13 40 ac 34 df 3d bf 9a 19 49 39 15 |"
When a particular level is specified, messages from all other levels of higher significance will be reported as well. 

E.g., when LogLevel info is specified, then messages with log levels of notice and warn will also be posted.

Using a level of at least crit is recommended.

For example:

LogLevel notice
When logging to a regular file, messages of the level notice cannot be suppressed and thus are always logged. However, this doesn't apply when logging is done using syslog.

Specifying a level without a module name will reset the level for all modules to that level. 

Specifying a level with a module name will set the level for that module only. 

It is possible to use the module source file name, the module identifier, or the module identifier with the trailing _module omitted as module specification. 

This means the following three specifications are equivalent:

LogLevel info ssl:warn
LogLevel info mod_ssl.c:warn
LogLevel info ssl_module:warn
It is also possible to change the level per directory:

LogLevel info
<Directory "/usr/local/apache/htdocs/app">
  LogLevel debug
Per directory loglevel configuration only affects messages that are logged after the request has been parsed and that are associated


Controls the verbosity of the ErrorLog - Apache HTTP Server Version 2.4
Test Your Knowledge in Computers #495
Difficulty: Easy
Blocks of code cannot be nested within each other to form sub-blocks.
True or False?

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to connect to FTP server which requires SSL authentication?

Hello, I tried searching through lot of threads for a solution but couldn't fetch the exact solution, so I am creating a new thread. I am trying to connect to a FTP server 1) using a simple FTP command, it gives the error : 534 Policy requires SSL. Login failed. 2) using SFTP... (19 Replies)
Discussion started by: amitshete
19 Replies

2. AIX

AIX Remote Connect Fail With “No more multiple IP addresses to connect” Error

We have a production server at a client site running AIX. And recently when users are trying to connect to it via telnet, it prompts "No more multiple IP addresses to connect". Can I know what does this error mean? and how to rectify this? Thanks. (2 Replies)
Discussion started by: a_sim
2 Replies

3. Web Development

Apache proxy for web app with ssl

I have a ubuntu server running subsonic as a web app. Currently the web interface is available from port 4040 for https connections and 4141 for https connections with the context /subsonic as follows: http://mydomain:4040/subsonic https://mydomain:4141/subsonic I would like to loose the port... (0 Replies)
Discussion started by: barrydocks
0 Replies

4. Web Development

Http connect to proxy to websockets

I am having a hard time with this one. We have a websocket server listening on port 80 at We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Discussion started by: glev2005
1 Replies

5. Web Development

Httpd proxy with mod_jk,ssl only on login page using .htacess

Hi all, I have a web app with the following pages, browse.jsp and shopping.jsp. I want to protect shopping.jsp with https. (https is only between browser and apache httpd server.)The https for the shopping.jsp page will terminate at the web server. From web server to tomcat application server... (0 Replies)
Discussion started by: new2ss
0 Replies

6. Programming

Failed SSL Connection Attempt

The below error message I started seeing using Ubuntu 14.04 and was wondering if the forum has seen it because I cant seem much on the net for this: perl -e 'use IO::Socket::SSL qw(debug3);IO::Socket::SSL->new(PeerAddr=>"",PeerPort=> 443,Proto=>"TCP") or die $!' DEBUG:... (1 Reply)
Discussion started by: metallica1973
1 Replies

7. Red Hat

Proxy tunneling failed: ForbiddenUnable to establish SSL connection.

Tryied both ways curl and wget wget --no-check-certificate --2017-05-05 17:29:02-- Connecting to myproxy:8080... connected. Proxy tunneling failed: ForbiddenUnable to establish SSL connection. curl curl: (56)... (3 Replies)
Discussion started by: charli1
3 Replies
PROXYTUNNEL(1)						      General Commands Manual						    PROXYTUNNEL(1)

proxytunnel - program to tunnel a connection throught an standard HTTPS proxy. SYNOPSIS
proxytunnel [options] DESCRIPTION
This manual page documents the proxytunnel command. proxytunnel is a program that open a tunnel through a HTTPS proxy. OPTIONS
This program follow the usual GNU command line syntax, with long options starting with two dashes (`-'). -h, --help Print help and exit. -V, --version Print the version of the program and exit. -i, --inetd Run from inetd. Default is off. -a PORT, --standalone=PORT Run as standalone daemon on specified port. -p host:port, --proxy=host:port The local HTTPS proxy host:port combo to connect to. -r host:port, --remproxy=host:port The second-level (remote) proxy host:port to connect to when using two proxies. -d host:port, --dest=host:port The destination host:port to built the tunnel to. -e, --encrypt Encrypt the data between the local proxy and the destination using SSL. -E, --encrypt-proxy Encrypt the data between the client and the local proxy using SSL. -B, --buggy-encrypt-proxy Encrypt the data between the client and the local proxy using SSL, but stop using SSL immediately after the CONNECT exchange to workaround server bugs. (Might not work on all setups; see /usr/share/doc/proxytunnel/README.Debian.gz for more details.) -X, --encrypt-remproxy Encrypt the data between the local proxy and the second-level proxy using SSL. -F STRING, --passfile=STRING The file containing Username & Password to send to HTTPS proxy for authentification. This file uses the same format as .wgetrc, and so can use the credentials in common with wget. This option can be used to at least hide the password from anyone clever enough to use the `ps' command. -P user:pass, --proxyauth=user:pass The credentials to use for local HTTP(S) proxy authentication. -R user:pass, --remproxyauth=user:pass The credentials to use for remote HTTP(S) proxy authentication. -N, --ntlm Use NTLM-based authentication. -t DOMAIN, --domain=DOMAIN The NTLM domain to use, default is to autodetect. -H STRING, --header=STRING Additional HTTP headers to send to the proxy. -x STRING, --proctitle=STRING Use a different process title. -v, --verbose Turn on verbosity. Default is off. -q, --quiet Suppress messages. Default is off. NOTES
To use this program with OpenSSH to connect to a host somewhere, create a $HOME/.ssh/config file with the following content: Host foobar ProtocolKeepAlives 30 ProxyCommand /usr/bin/proxytunnel -p -P user:password -d If your proxy doesn't require the username and password for using it, you can skip these options. If you want to run proxytunnel from inetd add the '--inetd' option. Most HTTPS proxies do not allow access to ports other than 443 (HTTPS) and 563 (SNEWS), so some hacking is necessary to start the SSH dae- mon on the required port. (On the server side add an extra Port statement in the sshd_config file) AUTHOR
This manual page was written by Loic Le Guyader <> and updated by Julian Gilbey <> for the Debian GNU/Linux system (but may be used by others). August 30, 2009 PROXYTUNNEL(1)

Featured Tech Videos

All times are GMT -4. The time now is 08:22 PM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy