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
Informations / Re: CWPpro version: vhost templates
« on: March 04, 2019, 02:39:18 PM »
this can't be any easier and simpler, there are also several instructions on the forum and wiki
Thanks for the link :D When I first updated to v0.9.8.742, all I realized was that the template editing functionality was removed from the admin. That's when I started editing each individual vhost. Back then (, I did not find any info on the new way of doing templates.

So it is normal behavior to manually assign a particular IP to an account but CWP does not automatically update the vhost files for the domains under that account?

Informations / Re: CWPpro version: vhost templates
« on: March 04, 2019, 02:07:24 PM »
I updated to CWPpro version: I don't seem to see the vhost templates. Can someone please point to me to it?
I posted about this earlier. This was a major change (I believe for the worse).

Now you have to edit each domain's vhost, manually.

Informations / Re: Add additional IP addresses to CWP 7
« on: March 04, 2019, 02:03:00 PM »
Did you edit the Apache hosts files and nginx config for each domain so they use the new IP? I don't know why CWP doesn't do this automatically. You would think it would but CWP associates the new IP to the user account(s) only.

PHP / Re: PHP info
« on: December 24, 2018, 02:05:48 PM »
Solved, its a nginx issues.
Can you provide more details about your solution?

My CWP panel is behind a gateway device so I have activated the NAT-ed network settings. I get this error when I use my public IP as my Shared IP. I do not get the error if I change my Shared IP to be the same as my NAT-ed IP but CWP Support is telling me that the Shared IP must be set to my public IP. The problem is that CWP uses the Shared IP to access the phpinfo.php file. The public IP should not be used to access the phpinfo.php file if you are NAT-ed!!!

How can this be fixed?

Same issue for me.

The vhost template menu is gone after this "upgrade". I lost all of the customization that I did. All vhosts were rebuilt and a really weird thing I found is that one account is supposed to use a different IP address. It shows that the correct IP is set to that account but when I check the vhost file for that account's domain, it's set to the shared IP. This sucks!

Thanks but I need different PHP versions per directory. Being limited to domain or subdomain will not be granular enough.

Can you specify PHP 7.2 for a domain and PHP 5.6 for a specific directory in the same domain with PHP-FMP?

The more I think about the authoritarian manner in which they pushed this update the more I'm leaning to going back to my previous control panel. This is BS! They need to do a better job of explaining the loss of "flexibility" if you take this "upgrade".

High Performance / Re: Wordpress - High-Performance instructions
« on: December 03, 2018, 12:02:27 AM »
If you switch to PHP-FMP, can you still have different PHP versions per directory, use htaccess to specify the version and have a php.ini per directory?

Same here.

I misunderstood the message and thought that I could install it as an option so I screwed up and installed it. Now I can't do anything because it says I need to rebuild my servers. This is BULLS!T the way they did this.

They did not elaborate on the advantages and disadvantages of PHP-FMP. After some research, it is my understanding that PHP-FMP does not let you have a different PHP version on a per directory basis, you can no longer have a seperate php.ini file per directory and you cannot specify which PHP version you want to use per directory, via htaccess files. Am I wrong? If I'm correct, then why in the world did the CWP developers say that PHP-FMP has, "flexibility and performance unlike anything else"? I'm guessing there's no way to undo this now  >:( >:( >:( >:( >:(

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?

Pages: [1] 2 3