Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jeffshead

Pages: [1] 2 3
Apache / Re: Definitive answer: HTTP to HTTPS www
« on: October 13, 2018, 10:59:44 AM »
No, it's not  :) You posted an Apache redirect. I stated that I changed my NGINX config to redirect. Are you using the redirect you posted with Apache & Varnish Cache & Nginx Reverse Proxy?

I could not get any http-to-httpswww Apache redirects to work (flawlessly) behind the NGINX reverse-proxy including the one that you posted. Some would loop and some would cause server errors. I'm also behind a web server firewall appliance so maybe that has something to do with it. The NGINX redirects work flawlessly and I believe that's where the redirects should be done since incoming traffic hits NGINX before it gets to Apache.

Apache / Re: Definitive answer: HTTP to HTTPS www
« on: October 12, 2018, 09:53:42 PM »
Thanks for the reply. I appreciate you taking the time :-)

I think you may have overlooked that I stated I'm using the NGINX reverse-proxy. I did figure out a way to make it work though.

I edited the NGINX vhosts templates so that I now have a 301 redirect from http to https and I added an additional server instance in the NGINX ssl vhost template so I now have a domain.tld and a www.domain.tld instance. The domain.tld server has a 301 redirect to www.domain.tld.

It works great!

FTP / Uploaded files missing code
« on: September 19, 2018, 12:55:58 PM »
Has anyone encountered an issue where the files you upload are cut off?

If I use a standard user FTP account and upload a full website, web app or even large, single files, sometimes some of the files are missing code. It's as if you open a file in a text editor and delete the bottom 1/3 of the file.

I havn't encountered this issue if I use the root account and SFTP to upload the same files or directories.

What could be causing this issue?

CentOS Configuration / Add additional IP Addresses
« on: August 20, 2018, 09:43:50 PM »
I am behind a UTM appliance so I have NAT enabled. I would like some domains to have their own IP address. I have specified for Default IP, Shared IP and NAT'ed IP.

I know how to add additional IP addresses to the server but how do I set up the config files for each domain?

I added IP address to the server and selected it for a particular user account. I want to use this IP address for a specific domain. I am using Apache, NGINX Reverse Proxy and Varnish. Do I have to manually change the IP address in all three server's config files? What about the Varnish config files? Do I have to create/add an additional secret for the new IP? What code do I add/edit and to what Varnish config file(s)?

Also, when I use Apache Settings->Rebuild Virtual Hosts, it uses for all domains even though I have specified for one of the user accounts. The Rebuild Virtual Hosts tool isn't designed to pull/insert the IP address assigned to each user account???

CentOS 7 Problems / Re: Apache + Varnish + Nginx . WordPress SSL issues
« on: August 11, 2018, 04:47:51 PM »
I had the same issue before. It was a pain. I tried so many solutions but none work for me but this one. I hope it will workout for you.

Add this "return 301 https://$host$request_uri;" to your "nginx_proxy_vhost" like below:
Code: [Select]
return 301 https://$host$request_uri;

location / {

That will redirect to https.

What if you want all traffic redirected to https://www.domain.tld?

I read that adding if statements in config files is frowned upon and that the best way is to add a separate server for domain.tld and one for www.domain.tld but I cannot get this to work.

I tried editing 'nginx_proxy_vhost_ssl' by removing YOURDOMAIN from server_name so only www.YOURDOMAIN remains and by adding another server directly below # Virtual host file starts here but it does not work.

Below is the top portion of my nginx_proxy_vhost_ssl template:
Code: [Select]
# Virtual host file starts here

# START of my edit to redirect to https://www.
server {
server_name YOURDOMAIN;
return 301 $scheme://www.YOURDOMAIN$request_uri;
# !!! IMPORTANT - also had to remove YOURDOMAIN from server_name, a few lines below.
# END of my edit to redirect to https://www.

server {
access_log /var/log/nginx/access.YOURDOMAIN.log;
error_log /var/log/nginx/error.YOURDOMAIN.log;
server_name www.YOURDOMAIN;

So does this mean you can have only one server in the template?

Apache / Definitive answer: HTTP to HTTPS www
« on: August 10, 2018, 01:11:19 PM »
I have been struggling with this for days but can't get this to work in all situations.

What is the proper way (per domian) to direct all traffic to https://www.domain.tld/:

http://domain.tld-> https://www.domain.tld/
http://www.domain.tld-> https://www.domain.tld/
https://domain.tld-> https://www.domain.tld/

I am using Apache & Varnish Cache & Nginx Reverse Proxy and AutoSSL. I have tried rewrites and redirects in .htaccess and in vhosts configs but I have been unsuccessful.

I know you can edit the vhost templates and I also see that you can have per domain, custom config files but what is the proper code and way of doing this so the configurations are not lost when CWP rebuilds the vhosts?

Help... I'm starting to hemorrhage!

CentOS-WebPanel Bugs / Re: Apache Builder (compiler) not working
« on: June 11, 2018, 11:46:06 AM »
I tried your suggestion and it worked however, Nginx fails to start because of the following error:

Code: [Select]
Jun 10 22:50:33 nginx[14455]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/pki/tls/private/") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)

There is nothing wrong with the cert or key. They both match.
I fixed this. The cert issued for the website needs to be added to the top of the bundle cert. My original bundle cert contained the intermediate and root certs, only.

However, the reason for creating this thread still needs to be fixed.

CentOS-WebPanel Bugs / Re: Apache Builder (compiler) not working
« on: June 11, 2018, 03:00:56 AM »
Noticed this thread so I tried it myself and got the same issues.

So I switched to apache+nginx+varnish and compiled again and it works.
Sorry to hear you have same issue but now I know it's definitely a CWP bug, as I suspected.

I tried your suggestion and it worked however, Nginx fails to start because of the following error:

Code: [Select]
Jun 10 22:50:33 nginx[14455]: nginx: [emerg] SSL_CTX_use_PrivateKey_file("/etc/pki/tls/private/") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)

There is nothing wrong with the cert or key. They both match.

Oh one thing I forgot to mentioned and not sure if this have any major issue.

Add the end of the log tail -f /var/log/apache-rebuild.log I did get this error.

Code: [Select]
Error:Can't add notification!
I get the same error.

Is support any better if you upgrade to Pro? There are some serious bugs and it seems Support does not moderate the forum very often.

CentOS-WebPanel Bugs / Re: Apache Builder (compiler) not working
« on: June 11, 2018, 01:50:32 AM »
It just does not work for me. I've tried over and over.

After I perform the rebuild and if I manually edit httpd.conf and replace all of the missing configurations and restart httpd, it still shows v.2.4.29.

CentOS-WebPanel Bugs / Re: Apache Builder (compiler) not working
« on: May 17, 2018, 12:37:16 AM »
Once compiling completes, Apache cannot start because httpd.conf is virtually blank except for a couple of lines (forgot to record those).

Below is contents of httpd.conf after rebuild:
Code: [Select]
ExtendedStatus On
Include /usr/local/apache/conf/sharedip.conf
Include /usr/local/apache/conf.d/*.conf

Below is contents before rebuild:
Code: [Select]
# This is the main Apache HTTP server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See <URL:> for detailed information.
# In particular, see
# <URL:>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do.  They're here only as hints or reminders.  If you are unsure
# consult the online docs. You have been warned. 
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.

# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path.  If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used.  If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
ServerRoot "/usr/local/apache"

# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
# Mutex default:logs

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
Listen 80

# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/
LoadModule authn_file_module modules/
#LoadModule authn_dbm_module modules/
#LoadModule authn_anon_module modules/
#LoadModule authn_dbd_module modules/
#LoadModule authn_socache_module modules/
LoadModule authn_core_module modules/
LoadModule authz_host_module modules/
LoadModule authz_groupfile_module modules/
LoadModule authz_user_module modules/
#LoadModule authz_dbm_module modules/
#LoadModule authz_owner_module modules/
#LoadModule authz_dbd_module modules/
LoadModule authz_core_module modules/
LoadModule access_compat_module modules/
LoadModule auth_basic_module modules/
#LoadModule auth_form_module modules/
#LoadModule auth_digest_module modules/
#LoadModule allowmethods_module modules/
#LoadModule file_cache_module modules/
#LoadModule cache_module modules/
#LoadModule cache_disk_module modules/
#LoadModule cache_socache_module modules/
#LoadModule socache_shmcb_module modules/
#LoadModule socache_dbm_module modules/
#LoadModule socache_memcache_module modules/
#LoadModule watchdog_module modules/
#LoadModule macro_module modules/
#LoadModule dbd_module modules/
#LoadModule dumpio_module modules/
#LoadModule buffer_module modules/
#LoadModule ratelimit_module modules/
LoadModule reqtimeout_module modules/
#LoadModule ext_filter_module modules/
#LoadModule request_module modules/
#LoadModule include_module modules/
LoadModule filter_module modules/
#LoadModule substitute_module modules/
#LoadModule sed_module modules/
#LoadModule deflate_module modules/
LoadModule mime_module modules/
LoadModule log_config_module modules/
#LoadModule log_debug_module modules/
#LoadModule logio_module modules/
LoadModule env_module modules/
#LoadModule expires_module modules/
LoadModule headers_module modules/
#LoadModule unique_id_module modules/
LoadModule setenvif_module modules/
LoadModule version_module modules/
#LoadModule remoteip_module modules/
#LoadModule proxy_module modules/
#LoadModule proxy_connect_module modules/
#LoadModule proxy_ftp_module modules/
#LoadModule proxy_http_module modules/
#LoadModule proxy_fcgi_module modules/
#LoadModule proxy_scgi_module modules/
#LoadModule proxy_fdpass_module modules/
#LoadModule proxy_wstunnel_module modules/
#LoadModule proxy_ajp_module modules/
#LoadModule proxy_balancer_module modules/
#LoadModule proxy_express_module modules/
#LoadModule proxy_hcheck_module modules/
#LoadModule session_module modules/
#LoadModule session_cookie_module modules/
#LoadModule session_crypto_module modules/
#LoadModule session_dbd_module modules/
#LoadModule slotmem_shm_module modules/
#LoadModule ssl_module modules/
#LoadModule lbmethod_byrequests_module modules/
#LoadModule lbmethod_bytraffic_module modules/
#LoadModule lbmethod_bybusyness_module modules/
#LoadModule lbmethod_heartbeat_module modules/
LoadModule unixd_module modules/
#LoadModule dav_module modules/
LoadModule status_module modules/
LoadModule autoindex_module modules/
#LoadModule asis_module modules/
#LoadModule info_module modules/
#LoadModule suexec_module modules/
#LoadModule cgid_module modules/
#LoadModule dav_fs_module modules/
#LoadModule vhost_alias_module modules/
#LoadModule negotiation_module modules/
LoadModule dir_module modules/
#LoadModule actions_module modules/
#LoadModule speling_module modules/
#LoadModule userdir_module modules/
LoadModule alias_module modules/
#LoadModule rewrite_module modules/

<IfModule unixd_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch. 
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User daemon
Group daemon


# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition.  These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.

# ServerAdmin: Your address, where problems with the server should be
# e-mailed.  This address appears on some server-generated pages, such
# as error documents.  e.g.

# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.

# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
<Directory />
    AllowOverride none
    Require all denied

# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.

# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/usr/local/apache/htdocs"
<Directory "/usr/local/apache/htdocs">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important.  Please see
    # for more information.
    Options Indexes FollowSymLinks

    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   AllowOverride FileInfo AuthConfig Limit
    AllowOverride None

    # Controls who can get stuff from this server.
    Require all granted

# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
    DirectoryIndex index.html

# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ".ht*">
    Require all denied

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "logs/error_log"

# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn

<IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common

    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio

    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here.  Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "logs/access_log" common

    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "logs/access_log" combined

<IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo

    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL.  You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.

    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client.  The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/usr/local/apache/cgi-bin/"


<IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock cgisock

# "/usr/local/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/usr/local/apache/cgi-bin">
    AllowOverride None
    Options None
    Require all granted

<IfModule headers_module>
    # Avoid passing HTTP_PROXY environment to CGI's on this or any proxied
    # backend servers which have lingering "httpoxy" defects.
    # 'Proxy' request header is undefined by the IETF, not listed by IANA
    RequestHeader unset Proxy early

<IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types

    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz

    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi

    # For type maps (negotiated resources):
    #AddHandler type-map var

    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml

# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type.  The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic

# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/"
#ErrorDocument 402

# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited

# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files.  This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#EnableMMAP off
#EnableSendfile on

# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
#Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin

Below is contents of var\log\apache-rebuild.log:

Anyone have any ideas?

CentOS-WebPanel Bugs / Apache Builder (compiler) not working
« on: May 11, 2018, 12:20:23 PM »
I tried to update Apache to latest version. The latest version in the drop-down list is 2.4.33:

Once compiling completes, Apache cannot start because httpd.conf is virtually blank except for a couple of lines (forgot to record those).

If I manually restore a backup of httpd.conf, Apache will start but it still shows it's version 2.4.29:

Am I missing a step?

CentOS-WebPanel Bugs / Simple PHP.ini editor does not work
« on: May 11, 2018, 01:44:44 AM »
When I edit the text in any of the text boxes on this page and click the save button, the edits do not stick.

If I make edits on the PHP.ini Configuration page or edit the php.ini directly, the edits do stick and they show up on the Simple PHP.ini editor page.

Warning: file_get_contents( failed to open stream: operation failed in /usr/local/cwpsrv/htdocs/resources/admin/modules/php_info.php on line 0

Same issue.

Tried recompiling PHP and Apache.

Installation / Re: How to use Clamd to scan uploaded files
« on: March 04, 2018, 12:13:20 AM »
I tried the following and it works:
Code: [Select]
clamscan /home/jeff/public_html/upload/

So why does clamdscan  /home/jeff/public_html/upload/ throw the connection refused error?

This is what I get when I run this command...
Code: [Select]
[root@cwp ~]# ps -aux | grep clamd
amavis   11012  0.0 14.4 717996 559656 ?       Ssl  09:40   0:22 /usr/sbin/clamd -c /etc/clamd.d/amavisd.conf --foreground=yes
root     20789  0.0  0.0 112660   980 pts/0    R+   18:50   0:00 grep --color=auto clamd
... so it appears that clamd is  running.

Installation / How to use Clamd to scan uploaded files
« on: March 02, 2018, 04:04:51 PM »
I disabled the postfix service because email for all domians hosted on CWP is handled by another server.

However, I would like to use ClamAV to scan files that are uploaded via some Perl web apps. I enabled and started 'clamd-scan.service' and 'clamd@scan.service'.

The scripts are not working and when I test via command line (e.g., clamdscan /home/jeff/public_html/uploads/, I get the following error:

Code: [Select]
ERROR: Could not connect to clamd on Connection refused

----------- SCAN SUMMARY -----------
Infected files: 0
Total errors: 1
Time: 0.011 sec (0 m 0 s)

I also tried enabling and starting 'amavisd.service' but I got the same error when testing.

Not sure what to look at next. Anyone have any ideas?

Pages: [1] 2 3