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.
361
CentOS 8 Problems / Re: PHP Switcher ERROR
« on: March 20, 2024, 11:22:37 PM »
Install a NON-beta operating system like AlmaLinux 8 like @overseer recommended and you won't have a problem.
CentOS 8 is dead, and has been dead. CentOS Stream is a beta operating system for RHEL.
Fedora is the alpha.
Fedora (alpha) -> Stream (beta) -> RHEL
CentOS 8 is dead, and has been dead. CentOS Stream is a beta operating system for RHEL.
Fedora is the alpha.
Fedora (alpha) -> Stream (beta) -> RHEL
362
CentOS 7 Problems / Re: CWP IP took too long to respond
« on: March 20, 2024, 09:32:01 PM »
Vultr probably has something blocked due to attacks.
If you have CSF disabled, then it's not CWP.
You will need to contact your ISP to find out why their network is blocked.
Or open a ticket Vultr and give them your local IP, and see what they say.
If you have CSF disabled, then it's not CWP.
You will need to contact your ISP to find out why their network is blocked.
Or open a ticket Vultr and give them your local IP, and see what they say.
364
CentOS 7 Problems / Re: CWP IP took too long to respond
« on: March 20, 2024, 09:22:49 PM »
Weird.
I'm getting an SSL error, but can say continue and access the login screen from the US.
I'm getting an SSL error, but can say continue and access the login screen from the US.
365
CentOS 7 Problems / Re: CWP IP took too long to respond
« on: March 20, 2024, 09:18:33 PM »
Also I just saw you are using Cloudflare. (Which is good when configured correctly)
Check your SSL settings there as well.
As that's probably where the problem is at.
Check your SSL settings there as well.
As that's probably where the problem is at.
366
CentOS 7 Problems / Re: CWP IP took too long to respond
« on: March 20, 2024, 09:15:13 PM »
For some reason it's not reaching Let's Encrypt to generate a SSL, it's only generating an internal SSL from CWP.
On the SSL error screen you can say to continue to the login screen.
Temporarily turn off the firewall, and try to generate it again.
Is this a new server install?
On the SSL error screen you can say to continue to the login screen.
Temporarily turn off the firewall, and try to generate it again.
Is this a new server install?
368
CentOS 7 Problems / Re: CWP IP took too long to respond
« on: March 20, 2024, 08:53:03 PM »
It's giving SSL certificate errors, try to access it with the server name at :2030, and see if the SSL certificate is still valid.
Is this Public or NAT?
What distro are you running?
Can you access the server via SSH?
If you can try running these from /scripts:
Is this Public or NAT?
What distro are you running?
Can you access the server via SSH?
If you can try running these from /scripts:
Code: [Select]
generate_hostname_ssl
hostname_ssl_restart_services
369
PHP / Re: INSTALL PHP 5.2.17 ON CWP
« on: March 20, 2024, 08:44:03 PM »
If this is the only site on the system, you could try to follow the guide and install PHP 5.2.x as PGP-CGI.
But not sure if it would work or not.
The download path for the last PHP 5.2.17 is http://museum.php.net/php5/php-5.2.17.tar.gz
But not sure if it would work or not.
The download path for the last PHP 5.2.17 is http://museum.php.net/php5/php-5.2.17.tar.gz
370
PHP / Re: INSTALL PHP 5.2.17 ON CWP
« on: March 20, 2024, 08:29:35 PM »
The lowest supported version of PHP on CWP is 5.3.x
371
DNS / Re: Postmark DKIM selector changes when SOA serial updates
« on: March 19, 2024, 10:21:41 PM »
Try to edit & save the RAW DNS file, and not use the GUI.
You can get to the RAW BIND file via:
Admin Panel -> DNS Functions -> List DNS Zones -> (domain name) Edit File
After making your changes, click Save File, and Restart BIND.
You can get to the RAW BIND file via:
Admin Panel -> DNS Functions -> List DNS Zones -> (domain name) Edit File
After making your changes, click Save File, and Restart BIND.
372
Nginx / Re: How to change apache LimitRequestFieldSize?
« on: March 19, 2024, 10:17:26 PM »
PHP Laravel is just an open-source server-side web framework language.
Has this ever worked?
Or did it just stop working one day?
Has this ever worked?
Or did it just stop working one day?
373
DNS / Re: IPV6 Support on CWP
« on: March 19, 2024, 10:14:00 PM »
Interesting little module, will have to test it out.
But most IPv6 allocations are /64, not /112.
But most IPv6 allocations are /64, not /112.
374
DNS / Re: Postmark DKIM selector changes when SOA serial updates
« on: March 19, 2024, 12:08:01 AM »
You should just have to create an additional DKIM, SPF for Postmark in the DNS that come from them.
e.g. postmark_domain TXT DKIM=(rest of DKIM)
Same for SPF.
If you try & change anything else, things will get messed up.
Here's a good article I found that guides you thru the DKIM & SPF records.
https://easydmarc.com/blog/postmark-spf-and-dkim-setup-step-by-step/
e.g. postmark_domain TXT DKIM=(rest of DKIM)
Same for SPF.
If you try & change anything else, things will get messed up.
Here's a good article I found that guides you thru the DKIM & SPF records.
https://easydmarc.com/blog/postmark-spf-and-dkim-setup-step-by-step/
375
DNS / Re: some problems only denic german domains
« on: March 16, 2024, 01:06:39 AM »
DNS GLUE Records are handled by your domain registrar usually.
I know godaddy and namecheap do.
It's usually recommended that you 2 different IP's on different servers for failover.
The domain name munichescorts.ml doesn't have any DNS listed according to Leaf DNS.
This isn't a problem with CWP, the registrar doesn't have any entries.
And this is from Many Tools (https://manytools.org/network/query-dns-records-online/):
private-escort-girls.de has NS listed:
--
DNS GLUE-Einträge werden normalerweise von Ihrem Domain-Registrar verwaltet.
Ich weiß, dass Godaddy und Namecheap das wissen.
Für das Failover wird normalerweise empfohlen, zwei verschiedene IP-Adressen auf verschiedenen Servern zu verwenden.
Für den Domainnamen munichescorts.ml ist gemäß Leaf DNS kein DNS aufgeführt.
Mit CWP ist das kein Problem, der Registrar hat keine Einträge.
Und das ist von Many Tools (https://manytools.org/network/query-dns-records-online/):
private-escort-girls.de hat NS gelistet:
I know godaddy and namecheap do.
It's usually recommended that you 2 different IP's on different servers for failover.
The domain name munichescorts.ml doesn't have any DNS listed according to Leaf DNS.
This isn't a problem with CWP, the registrar doesn't have any entries.
And this is from Many Tools (https://manytools.org/network/query-dns-records-online/):
Code: [Select]
"NS" DNS records for munichescorts.ml [Google DNS servers]:
No NS records found for munichescorts.ml [Google DNS servers].
(invalid Domain or DNS server?) -> DNS request failed: The domain name referenced in the query does not exist.private-escort-girls.de has NS listed:
Code: [Select]
"NS" DNS records for private-escort-girls.de [Google DNS servers]:
private-escort-girls.de. 21600 IN NS ns1072.ui-dns.biz.
private-escort-girls.de. 21600 IN NS ns1063.ui-dns.de.
private-escort-girls.de. 21600 IN NS ns1102.ui-dns.org.
private-escort-girls.de. 21600 IN NS ns1054.ui-dns.com.--
DNS GLUE-Einträge werden normalerweise von Ihrem Domain-Registrar verwaltet.
Ich weiß, dass Godaddy und Namecheap das wissen.
Für das Failover wird normalerweise empfohlen, zwei verschiedene IP-Adressen auf verschiedenen Servern zu verwenden.
Für den Domainnamen munichescorts.ml ist gemäß Leaf DNS kein DNS aufgeführt.
Mit CWP ist das kein Problem, der Registrar hat keine Einträge.
Und das ist von Many Tools (https://manytools.org/network/query-dns-records-online/):
Code: [Select]
"NS" DNS records for munichescorts.ml [Google DNS servers]:
No NS records found for munichescorts.ml [Google DNS servers].
(invalid Domain or DNS server?) -> DNS request failed: The domain name referenced in the query does not exist.private-escort-girls.de hat NS gelistet:
Code: [Select]
"NS" DNS records for private-escort-girls.de [Google DNS servers]:
private-escort-girls.de. 21600 IN NS ns1072.ui-dns.biz.
private-escort-girls.de. 21600 IN NS ns1063.ui-dns.de.
private-escort-girls.de. 21600 IN NS ns1102.ui-dns.org.
private-escort-girls.de. 21600 IN NS ns1054.ui-dns.com.
