Messages

1

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 07:02:31 PM »

i Commented the lines in httpd.ssl added ther server.crt and server.key into conf folder then chaged the port of https to 4433 and that works now my websites are live and have no issue thank you for help

2

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 06:05:06 PM »

Show output of:

Code: [Select]

/usr/local/apache/bin/httpd -v
and

Code: [Select]

cat /usr/local/apache/conf/extra/httpd-ssl.conf

[root@panel ~]# /usr/local/apache/bin/httpd -v
Server version: Apache/2.4.62 (Unix)
Server built:   Aug  7 2024 05:37:08





 [root@panel ~]# cat /usr/local/apache/conf/extra/httpd-ssl.conf
#
# This is the Apache server configuration file providing SSL support.
# It contains the configuration directives to instruct the server how to
# serve pages over an https connection. For detailed information about these
# directives see <URL:http://httpd.apache.org/docs/2.4/mod/mod_ssl.html>
#
# 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.
#
# Required modules: mod_log_config, mod_setenvif, mod_ssl,
#          socache_shmcb_module (for default value of SSLSessionCache)

#
# Pseudo Random Number Generator (PRNG):
# Configure one or more sources to seed the PRNG of the SSL library.
# The seed data should be of good random quality.
# WARNING! On some platforms /dev/random blocks if not enough entropy
# is available. This means you then cannot use the /dev/random device
# because it would lead to very long connection times (as long as
# it requires to make more entropy available). But usually those
# platforms additionally provide a /dev/urandom device which doesn't
# block. So, if available, use this one instead. Read the mod_ssl User
# Manual for more details.
#
#SSLRandomSeed startup file:/dev/random  512
#SSLRandomSeed startup file:/dev/urandom 512
#SSLRandomSeed connect file:/dev/random  512
#SSLRandomSeed connect file:/dev/urandom 512


#
# When we also provide SSL we have to listen to the
# standard HTTP port (see above) and to the HTTPS port
#
Listen 443

##
##  SSL Global Context
##
##  All SSL configuration in this context applies both to
##  the main server and all SSL-enabled virtual hosts.
##

#   SSL Cipher Suite:
#   List the ciphers that the client is permitted to negotiate,
#   and that httpd will negotiate as the client of a proxied server.
#   See the OpenSSL documentation for a complete list of ciphers, and
#   ensure these follow appropriate best practices for this deployment.
#   httpd 2.2.30, 2.4.13 and later force-disable aNULL, eNULL and EXP ciphers,
#   while OpenSSL disabled these by default in 0.9.8zf/1.0.0r/1.0.1m/1.0.2a.
SSLCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES
SSLProxyCipherSuite HIGH:MEDIUM:!MD5:!RC4:!3DES

#  By the end of 2016, only TLSv1.2 ciphers should remain in use.
#  Older ciphers should be disallowed as soon as possible, while the
#  kRSA ciphers do not offer forward secrecy.  These changes inhibit
#  older clients (such as IE6 SP2 or IE8 on Windows XP, or other legacy
#  non-browser tooling) from successfully connecting.
#
#  To restrict mod_ssl to use only TLSv1.2 ciphers, and disable
#  those protocols which do not support forward secrecy, replace
#  the SSLCipherSuite and SSLProxyCipherSuite directives above with
#  the following two directives, as soon as practical.
# SSLCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA
# SSLProxyCipherSuite HIGH:MEDIUM:!SSLv3:!kRSA

#   User agents such as web browsers are not configured for the user's
#   own preference of either security or performance, therefore this
#   must be the prerogative of the web server administrator who manages
#   cpu load versus confidentiality, so enforce the server's cipher order.
SSLHonorCipherOrder on

#   SSL Protocol support:
#   List the protocol versions which clients are allowed to connect with.
#   Disable SSLv3 by default (cf. RFC 7525 3.1.1).  TLSv1 (1.0) should be
#   disabled as quickly as practical.  By the end of 2016, only the TLSv1.2
#   protocol or later should remain in use.
SSLProtocol all -SSLv3
SSLProxyProtocol all -SSLv3

#   Pass Phrase Dialog:
#   Configure the pass phrase gathering process.
#   The filtering dialog program (`builtin' is an internal
#   terminal dialog) has to provide the pass phrase on stdout.
SSLPassPhraseDialog  builtin

#   Inter-Process Session Cache:
#   Configure the SSL Session Cache: First the mechanism
#   to use and second the expiring timeout (in seconds).
#SSLSessionCache         "dbm:/usr/local/apache/logs/ssl_scache"
SSLSessionCache        "shmcb:/usr/local/apache/logs/ssl_scache(512000)"
SSLSessionCacheTimeout  300

#   OCSP Stapling (requires OpenSSL 0.9.8h or later)
#
#   This feature is disabled by default and requires at least
#   the two directives SSLUseStapling and SSLStaplingCache.
#   Refer to the documentation on OCSP Stapling in the SSL/TLS
#   How-To for more information.
#
#   Enable stapling for all SSL-enabled servers:
#SSLUseStapling On

#   Define a relatively small cache for OCSP Stapling using
#   the same mechanism that is used for the SSL session cache
#   above.  If stapling is used with more than a few certificates,
#   the size may need to be increased.  (AH01929 will be logged.)
#SSLStaplingCache "shmcb:/usr/local/apache/logs/ssl_stapling(32768)"

#   Seconds before valid OCSP responses are expired from the cache
#SSLStaplingStandardCacheTimeout 3600

#   Seconds before invalid OCSP responses are expired from the cache
#SSLStaplingErrorCacheTimeout 600

##
## SSL Virtual Host Context
##

<VirtualHost _default_:443>

#   General setup for the virtual host
DocumentRoot "/usr/local/apache/htdocs"
ServerName www.example.com:443
ServerAdmin you@example.com
ErrorLog "/usr/local/apache/logs/error_log"
TransferLog "/usr/local/apache/logs/access_log"

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

#   Server Certificate:
#   Point SSLCertificateFile at a PEM encoded certificate.  If
#   the certificate is encrypted, then you will be prompted for a
#   pass phrase.  Note that a kill -HUP will prompt again.  Keep
#   in mind that if you have both an RSA and a DSA certificate you
#   can configure both in parallel (to also allow the use of DSA
#   ciphers, etc.)
#   Some ECC cipher suites (http://www.ietf.org/rfc/rfc4492.txt)
#   require an ECC certificate which can also be configured in
#   parallel.
SSLCertificateFile "/usr/local/apache/conf/server.crt"
#SSLCertificateFile "/usr/local/apache/conf/server-dsa.crt"
#SSLCertificateFile "/usr/local/apache/conf/server-ecc.crt"

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
#   ECC keys, when in use, can also be configured in parallel
SSLCertificateKeyFile "/usr/local/apache/conf/server.key"
#SSLCertificateKeyFile "/usr/local/apache/conf/server-dsa.key"
#SSLCertificateKeyFile "/usr/local/apache/conf/server-ecc.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 convenience.
#SSLCertificateChainFile "/usr/local/apache/conf/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 "/usr/local/apache/conf/ssl.crt"
#SSLCACertificateFile "/usr/local/apache/conf/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).
#   The CRL checking mode needs to be configured explicitly
#   through SSLCARevocationCheck (defaults to "none" otherwise).
#   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 "/usr/local/apache/conf/ssl.crl"
#SSLCARevocationFile "/usr/local/apache/conf/ssl.crl/ca-bundle.crl"
#SSLCARevocationCheck chain

#   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

#   TLS-SRP mutual authentication:
#   Enable TLS-SRP and set the path to the OpenSSL SRP verifier
#   file (containing login information for SRP user accounts).
#   Requires OpenSSL 1.0.1 or newer. See the mod_ssl FAQ for
#   detailed instructions on creating this file. Example:
#   "openssl srp -srpvfile /usr/local/apache/conf/passwd.srpv -add username"
#SSLSRPVerifierFile "/usr/local/apache/conf/passwd.srpv"

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#<Location />
#SSLRequire (    %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#            and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#            and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#            and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#            and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20       ) \
#           or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#</Location>

#   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 StrictRequire:
#     This denies access when "SSLRequireSSL" or "SSLRequire" applied even
#     under a "Satisfy any" situation, i.e. when it applies access is denied
#     and no other module can change it.
#   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/local/apache/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 sent or allowed to be 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-5]" \
         nokeepalive ssl-unclean-shutdown \
         downgrade-1.0 force-response-1.0

#   Per-Server Logging:
#   The home of a custom SSL log file. Use this when you want a
#   compact non-error SSL logfile on a virtual host basis.
CustomLog "/usr/local/apache/logs/ssl_request_log" \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

</VirtualHost>
[root@panel ~]#

3

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 05:41:57 PM »

Jan  3 17:40:36 panel systemd: Starting Web server Apache...
Jan  3 17:40:36 panel apachectl: AH00526: Syntax error on line 92 of /usr/local/apache/conf/extra/httpd-ssl.conf:
Jan  3 17:40:36 panel apachectl: SSLSessionCache: 'shmcb' session cache not supported (known names: ). Maybe you need to load the appropriate socache module (mod_socache_shmcb?).
Jan  3 17:40:36 panel systemd: httpd.service: control process exited, code=exited status=1
Jan  3 17:40:36 panel systemd: Failed to start Web server Apache.
Jan  3 17:40:36 panel systemd: Unit httpd.service entered failed state.
Jan  3 17:40:36 panel systemd: httpd.service failed.

4

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 05:20:45 PM »

Rename the file:

/usr/local/apache/conf.d/rpaf.conf
to
/usr/local/apache/conf.d/rpaf.conf_backup

and try to restart apache again.

Did you reinstall apache or some apache modules manually ?

Also, it seems you use Centos 7. Centos 7 is EOL. So be ready to experience problems when you update/install some server side software.

Thank you website are load but in http not https SSl was created when i try to create SSL if a domain it goaes back to Connection Refused i think ther is a problem to 443 port it is not accpting the connecton and webs site doesnt load

5

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 03:27:09 PM »

Jan  3 15:26:15 panel systemd: Starting Web server Apache...
Jan  3 15:26:15 panel apachectl: httpd: Syntax error on line 513 of /usr/local/apache/conf/httpd.conf: Syntax error on line 2 of /usr/local/apache/conf.d/rpaf.conf: Cannot load modules/mod_rpaf.so into server: /usr/local/apache/modules/mod_rpaf.so: cannot open shared object file: No such file or directory
Jan  3 15:26:15 panel systemd: httpd.service: control process exited, code=exited status=1
Jan  3 15:26:15 panel systemd: Failed to start Web server Apache.
Jan  3 15:26:15 panel systemd: Unit httpd.service entered failed state.
Jan  3 15:26:15 panel systemd: httpd.service failed.

Error

6

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 09:56:07 AM »

The main apache conf file looks good, except the line:
#Include /usr/local/apache/conf.d/*.conf
(last line of the file)
Uncomment it, stop/kill Apache and then try to restart it manually.

If your sites are inaccessible still then make sure the ports 80, 443 are used by Apache only:

Code: [Select]

netstat -nlp| egrep "nginx|httpd"If the ports 80, 443 remain unused then log into CWP admin and double check CWP is configured to use Apache only (WebServer config --> Select WebServers), switch to "Apache Only" if there is something else, rebuild vHosts and restart Apache.

I did everything nothing works my webservers are Apache only and i hae rebuilded the vhost nothin works

7

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 03, 2025, 06:50:08 AM »

Some of my domains are not here they are somewhere else please see
https://thcawholesale.me/
https://dirtbikes-officials.com/
Yes i am using centos DNS
my website loads on http but my files are in https my 443 says connection refused
and 80 port shows test page

8

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 02, 2025, 07:22:10 PM »

There are some vhosts in Ningx vhost folder as i am not using Ningx
I am Using apache only
I foud out that my 443 port connection refusedall web serving on 80 port when i removes the https and add http the web shows me Test page when i add https it says connection refued be it cant find the files
i thing thre is problem aslo with that screenshot attaced

Httpd.conf https://codepen.io/sohailfarooq356/pen/raBYBwb

 https://ibb.co/wQJPztk
https://ibb.co/NxtR716
https://ibb.co/VWVXpP0

9

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 02, 2025, 01:25:56 PM »

Here are all the screenshots
Apache is running but the connection refused

https://ibb.co/88ZhN3K
https://ibb.co/WpTc2KK
https://ibb.co/1LKGY00
My httpd.conf
https://codepen.io/sohailfarooq356/pen/raBYBwb

10

CentOS 7 Problems / Re: My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 02, 2025, 09:25:10 AM »

When i revert back to Apache nothing show up in Website when i chage the servers to ningx+apache ttest page shows up on all websites is there a probleem with htdocs i think they are blocked i cant acces the Test page also i want to use apache only

11

CentOS 7 Problems / My CWP websites are not loading after i changed my webservers to Ningx + Apache

« on: January 01, 2025, 06:48:57 PM »

My CWP websites are not loading after I changed my webservers to Ningx + Apache
Then I changed back to Apache nothing changes CWP user and CWP Admin in working i can access that but when open on of my website in browser Google Chrome says connection refused
on some users it says forbidden you dont have access
when i check DNS it goes to IP but my server refused the request


What i Have tried
1. Fix permissons
2. Rebuld Vhosts
3. Restart DNS
4. SSL Rebuid
5. tUrn Off Firewall
6. Disable Mod
Etc
But no Luck Cn you please help me with this quickly