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.
Pages: [1] 2
1
SSL / How to Prevent a Subdomain from Auto Installing SSL
« on: April 06, 2021, 07:48:14 PM »
Hi guys, I need some guidance here:
I have a subdomain which is redirected externally to another site with its own SSL certificate.
I deleted the auto-SSL by Let's Encrypt, in CentOS, but after few hours the subdomain keeps getting the Let's Encrypt SSL certificate auto installed.
This situation is causing "Not-secure-site" issues, because the external site's certificate is issued to a different URL than my subdomain https://prnt.sc/115yinb
What can I do to use my subdomain in the URL bar, but pointing to the external (secured) site?
I have a subdomain which is redirected externally to another site with its own SSL certificate.
I deleted the auto-SSL by Let's Encrypt, in CentOS, but after few hours the subdomain keeps getting the Let's Encrypt SSL certificate auto installed.
This situation is causing "Not-secure-site" issues, because the external site's certificate is issued to a different URL than my subdomain https://prnt.sc/115yinb
What can I do to use my subdomain in the URL bar, but pointing to the external (secured) site?
3
Backup / Re: All backups failing to run correctly
« on: March 02, 2021, 07:45:22 PM »
Indeed https://prnt.sc/10biyzk
4
Backup / Re: All backups failing to run correctly
« on: March 02, 2021, 05:05:13 PM »
That's weird, but no, it's still not working for us.
Is there any update from CWP about this issue?
Is there any update from CWP about this issue?
5
Backup / Re: All backups failing to run correctly
« on: February 18, 2021, 04:04:50 PM »
still not working for me; just the manual Full-backup works but the "Automatic Backup" is not working.
FYI, I'm in a pro license
FYI, I'm in a pro license
6
CSF Firewall / Re: CSF Firewall not Allowing Incoming PING
« on: February 04, 2021, 09:35:26 PM »
Resolved this issue in AWS EC2, by adding a Firewall Rule for All ICMP - IPv4 to the Security Group
7
CentOS 7 Problems / Re: Domain Redirect
« on: January 31, 2021, 06:10:29 PM »
@josemnunez would you have a workaround for this kind of situations
Please check if you have a redirect already captured in .htaccess
I have a similar problem, but I have CWP7.pro license and JUST Apache server (no Apache-Ngnix and Vanish) and when trying to redirect a subdomain to a specific page, it's not working.
The .htaccess file looks like:QuoteRewriteEngine on
RewriteOptions inherit
RewriteCond %{HTTP_HOST} ^www\.subdomain\.domain\.tld$
RewriteRule ^$ "https\:\/\/domain\.tld\/specific-page" [R=301,L]
8
CentOS 7 Problems / Re: Domain Redirect
« on: January 31, 2021, 07:20:41 AM »Please check if you have a redirect already captured in .htaccess
I have a similar problem, but I have CWP7.pro license and JUST Apache server (no Apache-Ngnix and Vanish) and when trying to redirect a subdomain to a specific page, it's not working.
The .htaccess file looks like:
Quote
RewriteEngine on
RewriteOptions inherit
RewriteCond %{HTTP_HOST} ^www\.subdomain\.domain\.tld$
RewriteRule ^$ "https\:\/\/domain\.tld\/specific-page" [R=301,L]
9
DNS / Re: BIND DNS Server Fail when Adding google._domainkey
« on: January 18, 2021, 06:16:30 PM »
@cynique you are a GENIOUS.
It did work; thank you!
It did work; thank you!
10
DNS / Re: BIND DNS Server Fail when Adding google._domainkey
« on: January 18, 2021, 06:00:04 PM »
@cynique sorry for the "silly" question, but how can a DNS record be split it without breaking it?
11
DNS / Re: BIND DNS Server Fail when Adding google._domainkey
« on: January 18, 2021, 04:28:59 PM »
Thanks and that's the problem, I don't see the error in what Google sent me to enter:
google._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgid3fOVOc2s3fxaASywa9VK3Z49CElqqEYiJx4kAkGD6qpUKTY487OBR3L1L1wFLk2NWWJpn+xpFj5P/070TJfWv3mAKt2YZr/woHgxV+HWNixB46TDBOcNmcY5hZJsrAO7CXMgAppzVgmBgBC7K66U0CMqfpeQZQ5G198AY3cHhIduj/XksbD8EQXHxxe0mUiiCpQSiB54H0JddnFT80z03WYP59xKCwVFNh3h5Aq/Ai64nT9crjGh7uQNJQqI+gqFDgUMgMKdE8VhjlLe526lM2akA1N79TuM2UA6Rq0nAWLpq2xPCsTqN6gVzBlMCId7wo1rUpmvh6e+nAMMRXwIDAQAB"
Can you spot it?
google._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgid3fOVOc2s3fxaASywa9VK3Z49CElqqEYiJx4kAkGD6qpUKTY487OBR3L1L1wFLk2NWWJpn+xpFj5P/070TJfWv3mAKt2YZr/woHgxV+HWNixB46TDBOcNmcY5hZJsrAO7CXMgAppzVgmBgBC7K66U0CMqfpeQZQ5G198AY3cHhIduj/XksbD8EQXHxxe0mUiiCpQSiB54H0JddnFT80z03WYP59xKCwVFNh3h5Aq/Ai64nT9crjGh7uQNJQqI+gqFDgUMgMKdE8VhjlLe526lM2akA1N79TuM2UA6Rq0nAWLpq2xPCsTqN6gVzBlMCId7wo1rUpmvh6e+nAMMRXwIDAQAB"
Can you spot it?
12
DNS / BIND DNS Server Fail when Adding google._domainkey
« on: January 18, 2021, 07:16:35 AM »
Could somebody advise?
We're trying to add google._domainkey TXT record, as instructed by Google where we have our Mail server, and the record is added fine through the DNS file editor, but when restarting BIND DNS, we receive this warning: https://prnt.sc/x3t9cx
The only domain key allowed is the default._domainkey; removing the default._domainkey and just leaving google._domainkey, leaving both don't work either.
This is what the journalctl -xe shows:
Jan 17 23:01:22 host.domain.tld systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun starting up.
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost.localdomain/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 0.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone domain.tld/IN: loaded serial 2021010424
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns1.domain.tld/IN: loaded serial 2020122901
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns2.domain.tld/IN: loaded serial 2020122900
Jan 17 23:01:22 host.domain.tld bash[22531]: zone host.domain.tld/IN: loaded serial 2020122996
Jan 17 23:01:22 host.domain.tld bash[22531]: dns_rdata_fromtext: /var/named/DOMAIN.WITH.ISSUE.db:23: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: loading from master file /var/named/DOMAIN.WITH.ISSUE.db failed: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: not loaded due to errors.
Jan 17 23:01:22 host.domain.tld bash[22531]: _default/DOMAIN.WITH.ISSUE/IN: syntax error
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service: control process exited, code=exited status=1
Jan 17 23:01:22 host.domain.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Jan 17 23:01:22 host.domain.tld systemd[1]: Unit named.service entered failed state.
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service failed.
Jan 17 23:01:25 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:25 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=39110 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:01:25 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:25 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:41 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:41 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=49734 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:00 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:02:00 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:02:00 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:02:00 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=59062 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:01 host.domain.tld systemd[1]: Created slice User Slice of securev.
-- Subject: Unit user-1001.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-1001.slice has finished starting up.
--
-- The start-up result is done.
Appreciate your prompt response.
We're trying to add google._domainkey TXT record, as instructed by Google where we have our Mail server, and the record is added fine through the DNS file editor, but when restarting BIND DNS, we receive this warning: https://prnt.sc/x3t9cx
The only domain key allowed is the default._domainkey; removing the default._domainkey and just leaving google._domainkey, leaving both don't work either.
This is what the journalctl -xe shows:
Jan 17 23:01:22 host.domain.tld systemd[1]: Starting Berkeley Internet Name Domain (DNS)...
-- Subject: Unit named.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has begun starting up.
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost.localdomain/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone localhost/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone 0.in-addr.arpa/IN: loaded serial 0
Jan 17 23:01:22 host.domain.tld bash[22531]: zone domain.tld/IN: loaded serial 2021010424
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns1.domain.tld/IN: loaded serial 2020122901
Jan 17 23:01:22 host.domain.tld bash[22531]: zone ns2.domain.tld/IN: loaded serial 2020122900
Jan 17 23:01:22 host.domain.tld bash[22531]: zone host.domain.tld/IN: loaded serial 2020122996
Jan 17 23:01:22 host.domain.tld bash[22531]: dns_rdata_fromtext: /var/named/DOMAIN.WITH.ISSUE.db:23: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: loading from master file /var/named/DOMAIN.WITH.ISSUE.db failed: syntax error
Jan 17 23:01:22 host.domain.tld bash[22531]: zone DOMAIN.WITH.ISSUE/IN: not loaded due to errors.
Jan 17 23:01:22 host.domain.tld bash[22531]: _default/DOMAIN.WITH.ISSUE/IN: syntax error
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service: control process exited, code=exited status=1
Jan 17 23:01:22 host.domain.tld systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
-- Subject: Unit named.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit named.service has failed.
--
-- The result is failed.
Jan 17 23:01:22 host.domain.tld systemd[1]: Unit named.service entered failed state.
Jan 17 23:01:22 host.domain.tld systemd[1]: named.service failed.
Jan 17 23:01:25 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:25 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=39110 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:01:25 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:25 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:01:41 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:01:41 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:01:41 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=49734 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:00 host.domain.tld dhclient[828]: DHCPREQUEST on eth0 to 172.31.0.1 port 67 (xid=0xd444f49)
Jan 17 23:02:00 host.domain.tld dhclient[828]: send_packet: Operation not permitted
Jan 17 23:02:00 host.domain.tld dhclient[828]: dhclient.c:2717: Failed to send 300 byte long packet over fallback interface.
Jan 17 23:02:00 host.domain.tld kernel: Firewall: *UDP_OUT Blocked* IN= OUT=eth0 SRC=172.31.13.28 DST=172.31.0.1 LEN=328 TOS=0x00 PREC=0x00 TTL=64 ID=59062 DF PROTO=UDP SPT=68 DPT=67 LEN=308 UID=0 GID=0
Jan 17 23:02:01 host.domain.tld systemd[1]: Created slice User Slice of securev.
-- Subject: Unit user-1001.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit user-1001.slice has finished starting up.
--
-- The start-up result is done.
Appreciate your prompt response.
13
CSF Firewall / CSF Firewall not Allowing Incoming PING
« on: January 18, 2021, 06:51:40 AM »
Although the settings in /etc/csf/csf.conf are as recommended to allow incoming PING, is not working as it should be.
# Allow incoming PING. Disabling PING will likely break external uptime
# monitoring
ICMP_IN = "1"
Results:
https://prnt.sc/x3rnn3
Any idea what else should be enable?
# Allow incoming PING. Disabling PING will likely break external uptime
# monitoring
ICMP_IN = "1"
Results:
https://prnt.sc/x3rnn3
Any idea what else should be enable?
14
Other / Re: Warning Database connection errorSQLSTATE[HY000] [1045] Access denied for user
« on: January 15, 2021, 01:21:56 AM »
Thank you;
WISECP customer support helped reinstalling the app.
WISECP customer support helped reinstalling the app.
15
Other / Warning Database connection errorSQLSTATE[HY000] [1045] Access denied for user
« on: January 06, 2021, 12:04:27 AM »
Hi there,
Does anybody has experience installing WiseCP, the billing plugin, in CentOS 7?
I followed instructions on https://docs.wisecp.com/en/kb/installation, but after entering the database information in wisecp installation startup, I got this warning:
Warning
Database connection errorSQLSTATE[HY000] [1045] Access denied for user 'database-user'@'localhost' (using password: YES)
I already have the latest CWP7pro.admin version.
I'd appreciate any advice as CWP will not help with 3rd-party installations, if not paying the Enterprise support; unless they accept a one-time support for this
Does anybody has experience installing WiseCP, the billing plugin, in CentOS 7?
I followed instructions on https://docs.wisecp.com/en/kb/installation, but after entering the database information in wisecp installation startup, I got this warning:
Warning
Database connection errorSQLSTATE[HY000] [1045] Access denied for user 'database-user'@'localhost' (using password: YES)
I already have the latest CWP7pro.admin version.
I'd appreciate any advice as CWP will not help with 3rd-party installations, if not paying the Enterprise support; unless they accept a one-time support for this
Pages: [1] 2