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 - AdventureTime

Pages: 1 2 [3] 4
31
PHP / Re: 502 Bad Gateway
« on: March 11, 2022, 03:08:57 AM »
Code: [Select]
I am still receiving a 403 message whenever I visit my site both SSL and non-SSL version of it.
Do you have mod_security enabled by any chance? It may be blocking a script that runs when you visit the page?
Either way, 403 message is usually user related. Meaning you added something that's blocking you.

Yes, I have mod_security enabled.
Also, the 403 message started to appear when I used AutoSSL and received the Let's Encrypt certificate.

32
PHP / Re: 502 Bad Gateway
« on: March 10, 2022, 04:07:32 PM »
Main config is for ALL of your accounts that don't have specific configurations.  Domain Config allows you to use a different template for an individual account or domain.  Once you explore some more, you will get the hang of it.

I thought it was something that would be mandatory for domains to have. At least now I know. I don't wholly understand the template's purpose, but I think either I will use default or php-fpm as the template, right?


Yes.  Set the Main config to Default is fine.  I

As to the Domain Configs, let's say you have a Joomla site, that requires specific settings from apache or nginx.  You can create a new template with those specific settings, and set that domain to use it.  NEVER edit the config files directly, because any changes made can be overwritten on an update of CWP, or a config rebuild

Thank you!

I activated the AutoSSL feature through Let's Encrypt.
Now I always receive a 403 Forbidden message.
I changed the type of web server from nginx + Varnish Cache to nginx only, vice-versa.

I am still receiving a 403 message whenever I visit my site both SSL and non-SSL version of it.

33
PHP / Re: 502 Bad Gateway
« on: March 10, 2022, 08:51:06 AM »
Main config is for ALL of your accounts that don't have specific configurations.  Domain Config allows you to use a different template for an individual account or domain.  Once you explore some more, you will get the hang of it.

I thought it was something that would be mandatory for domains to have. At least now I know. I don't wholly understand the template's purpose, but I think either I will use default or php-fpm as the template, right?

34
PHP / Re: 502 Bad Gateway
« on: March 10, 2022, 06:58:00 AM »
You may need to rebuild your configs after enabling fpm

I found the issue. I tried to explore these first:



I honestly don't know the difference between the two.

Moving forward, I checked the User Accounts > List Accounts and I noticed the Domain Name has a missing .com that is why it does not work. I fixed it by deleting and recreating the User Account again.
To my surprise, it worked. To be sure, I did the Fix Permissions stuff and Web Server Settings > Web Servers Main Conf / Web Servers Domain Conf.

Finally, it worked!

35
PHP / Re: 502 Bad Gateway
« on: March 10, 2022, 05:49:23 AM »
Please make sure you have a pro license, or any verison of FPM will be disabled automatically.  If you do have pro, make sure you start the PHP-FPM service

systemctl start php-fpm74
systemctl enable php-fpm74

I am happy to say that I am now using the pro version.



However, I only see the following even after enabling PHP-FPM


36
PHP / 502 Bad Gateway
« on: March 10, 2022, 05:15:44 AM »
Hello,

I have installed PHP-FPM and changed my webserver from Apache to either Nginx or Nginx + Varnish Cache. However, I am receiving a 502 Bad Gateway message for my website, which is the initial installation of WordPress.

I have selected the latest version of PHP, which is something like 7.4.28.

May you please help me?

Thanks!

37
CSF Firewall / Re: How to make WireGuard work?
« on: March 10, 2022, 04:49:32 AM »
- You cant have php-fpm without a pro license.

I just got my license for the entire year ;D I am thrilled.





I am delighted to support this excellent app.

UDP_IN and UDP_OUT should have port 51194 added to start, then restart the firewall with csf -r

Thank you for this!

38
CSF Firewall / Re: How to make WireGuard work?
« on: March 10, 2022, 03:09:10 AM »
- You cant have php-fpm without a pro license.

- To open port in firewall; Edit /etc/csf/csf.conf
Find TCP_IN, TCP_OUT, UDP_IN, UDP_OUT and put the port there depending on if the port is TCP/UDP or if it should be in input or output, then restart the firewall.

- Check in Admin CP if the scripts are getting blocked by Mod_security:
Security - Security Center - Security incidents tab.

Thank you. May you guide me what to write in the csf.conf file?
Also, what will I do if I see it under Mod_Security?

39
CSF Firewall / How to make WireGuard work?
« on: March 09, 2022, 04:10:53 PM »
Hello,

I believe this is my first post for the year 2022. And I must say I am delighted with how CWP makes everything easy to use. Although I can't get nginx with PHP-fpm to work without a CWP Pro account, I plan to support this unique and hassle-free cPanel-like experience. However, I also needed to have a VPN, so I decided to post my inquiry here.

I am a fan of WireGuard; ever since I have tried it out, I decided to stick to it instead of OpenVPN. I tried the scripts of Nyr and agristan to install WireGuard, and none of them worked after installing CWP and activating the three security features, Mod Security, Firewall, and Hidden Processes.

The good news is, before installing CWP, all of them worked fine. During the installation of WireGuard, I noticed the port is 51820, so I wonder how to allow it in CWP.

Thanks!

40
Installation / Inquiry regarding the custom installation
« on: April 04, 2016, 12:02:04 PM »
Hello,

Would it be possible to install CentOS Web Panel that only uses nginx and nothing else? Like, completely bypass Apache?

nginx + mariadb + (no mail stuff to be installed or antivirus for mail) + firewall + comodo waf + let's encrypt (gui?) + php7 (stable)

I'll be waiting for your reply.

Thanks.

41
DNS / Managed DNS Integration.
« on: November 28, 2015, 06:06:26 PM »
Hello,

Is there a way to integrate CloudFlare (free) inside CentOS Web Panel?

Thanks.

42
PHP / Re: Is it possible to use HHVM?
« on: November 04, 2015, 12:21:24 PM »
Hello.

Yes, you can using it, but you should install it manually.

Thank you. How? Apache uses suPHP by default.

43
Mod_Security / Newbie inquiry regarding Mod_Security and Comodo WAF.
« on: November 04, 2015, 02:41:16 AM »
Hello,

I have installed Mod_Security from this article. It is because when I was using the built-in installer from CentOS WebPanel, some functions of my WordPress websites does not work even if I have done rebuilding Apache and rebuilding the vHost again. Now, I was able to install both Mod_Security and Comodo WAF. My question is, do I have to turn on the built-in firewall protection of CentOS WebPanel aside from the protections offered by Mod_Security and Comodo WAF?

Thanks.

44
PHP / Is it possible to use HHVM?
« on: November 04, 2015, 02:36:10 AM »
Hello,

I was just wondering how can I install and use HHVM? I am currently using Apache, Varnish and nginx. I activated the three of them through CentOS WebPanel. Now, I am looking forward to serve pages faster and with less memory. Is there a way I can utilize HHVM?

Thanks.

45
CentOS-WebPanel Bugs / CentOS Web Panel causing the issue?
« on: August 08, 2015, 07:45:17 PM »
Hello,

I noticed all my websites hosted under my OVH Dedicated Server are always not working properly. Then after checking the control panel, I was shocked that the "Anti-DDoS" protection actually "blocked" my IPs and I have no idea why.

I just have 2 CentOS Web Panel installation. The first one uses Apache with Varnish, and the second one uses Varnish, nginx and Apache.

Anyway, for reference, here are the logs of OVH regarding the DDoS attacks.

Code: [Select]
Attack detail : 113Kpps/100Mbps
dateTime                   srcIp:srcPort           dstIp:dstPort           protocol flags       bytes reason               
2015.08.08 18:45:24 CEST   167.X.X.69:19343    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:52574    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:60099    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:32168    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:40814    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:3550     61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:3519     61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:24980    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:51592    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:30214    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:49539    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:45648    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:2619     61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:24919    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:53093    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:37711    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:16872    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:19043    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:33666    61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:45:24 CEST   167.X.X.69:7683     61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN

Code: [Select]
Attack detail : 101Kpps/91Mbps
dateTime                   srcIp:srcPort           dstIp:dstPort           protocol flags       bytes reason               
2015.08.08 18:48:43 CEST   198.X.X.47:26756      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:56316      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:35233      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:56013      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:43843      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:65193      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:33684      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:5957       61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:55075      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:54670      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:55055      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:63289      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:27728      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:58513      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:30378      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:48607      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:46149      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:45119      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:20494      61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN       
2015.08.08 18:48:43 CEST   198.X.X.47:7498       61.174.49.99:80         TCP      SYN           936 ATTACK:TCP_SYN

Thanks.

Pages: 1 2 [3] 4