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

Pages: 1 2 [3] 4 5
Installation / Is my server worthy?
« on: April 27, 2020, 09:27:03 PM »
I'm installing a second server at a new location and wondered if I could ask your opinion.

The server is a Dell PowerEdge T310.
I'm not running a raid but have three drives installed:
Root (primary drive) 100gb SATA2
2 x 500gb SATA2
8gb DDR3 (planning on upgrading to 16gb)
2.40GHz X3430 4-Cores

and this is connected to fibre optics at 20mb up and 75mb down stream.
The website will be a Wordpress backbone with WooCommerce
There will be an ad campaign through email as well

I plan to run a takeaway ordering website for our local area. I'm expecting about 500+ users to be browsing the site at once with about 100 actually ordering at once.
Can you see any obvious bottlenecks with this setup or recommendations or anything that needs to be planned in relation to hardware or CWP

CentOS 7 Problems / Re: 504 Gateway timeout error
« on: April 10, 2020, 04:00:08 PM »
Hi and thanks for the reply.
According to the API I'm running CGI

But I'm running forced PHP-FPM would that also be an issue?

CentOS 7 Problems / 504 Gateway timeout error
« on: April 09, 2020, 05:41:13 PM »
Apologies if this is in the wrong forum, and if so can I request an admin to relocate it please.
I'm hosting a Woocommerce website on one of my CWP servers and part of the shop ordering process is that when the customer orders a meal they get a popup telling them that the restaurant will either accept or cancel their order. The message keeps refreshing whilst it is waiting for a response from the restaurant kitchen to click at their end to accept the order or not.
If this process takes a little longer than expected, the customer gets a 504 Gateway Timeout error and the popup dissappears leaving the customer unaware if their order is coming or not.
Am I right in thinking that somewhere I need to increase the wait time on the server in order to give this app more time. If so has anyone any idea where this would be.
I'm running PHP 7.3, nginx-varnish-apache. Apache version 2.4.39

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 10:23:01 PM »

I did manage it once for one of my domains. FQD along with DNS... but it took me a while and I think it turned me blind a bit. Perhaps now that we are all in a lockdown I might try with this domain :)

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 10:03:15 PM »
Incorrect should'nt have the '@'
The At Symbol is as special case, only used by some DNS providers, to define the default host eg. @ A 123.456.123.456

Thank you :)

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 10:01:08 PM »
I have had a lot of issues trying to glue records so that I can have a (like my domain) but as I said I'm not so good with DNS and opted to have CWP host that for me. Yeah the name sucks but it is better than loosing the domain in the depths of the internet having lost the glue  ;) :) ;D

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 09:44:34 PM »
Ah all good. Thanks for the reply :)

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 09:33:24 PM »
No that is the genuine NS

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 09:13:24 PM »
Thanks ejsolutions
I couldn't work out hoe CNAMES can redirect. My DNS knowledge is limited.
I've added the domain to CNAMES but I didn't get the result I was expecting. So I placed a redirect in htdocs.... is that still acceptable?

CentOS 7 Problems / Re: using www I get site untrusted warning
« on: April 03, 2020, 07:19:49 PM »
Hi pixelpadre thanks for the quick reply.
Yes that is correct:

CentOS 7 Problems / using www I get site untrusted warning
« on: April 03, 2020, 06:59:08 PM »
Hi guy's.. This has baffled me for a while and I'm trying to work out what I've done or not.
Basically if a user visits our website using they get the padlock and all is well. However, if they visit the website with https:/ they get a warning that the site might be bogus and you shouldn't trust it.
Any ideas what I need to do.

SSL / Re: Only authorised on 8443
« on: February 09, 2020, 04:53:05 PM »
Thanks for all the replies and help with this.
I have found the issue and it was nothing to do with CWP. It turns out that I didn't check the external router properly and port 443 was occupied by the printer... I can't believe that I didn't check that thoroughly enough.
SSL is working correctly on port 443 for the domain

Thanks again for all your help

SSL / Re: Only authorised on 8443
« on: February 06, 2020, 09:04:54 AM »
Thanks for the suggestion. I have rebuilt the VHosts and still get the same issue. I also reconfigured the webserver to a basic Apache setup, but still get the same issue.

No SSL certificates were found on Make sure that the name resolves to the correct server and that the SSL port (default is 443) is open on your server's firewall.

SSL / Only authorised on 8443
« on: February 05, 2020, 01:58:51 PM »
Hi guys, I can't seem to find the answer to this in the forum. I running Nginx varnish Apache and have previously had SSL set up and running fine. Today the website was showing as unsecure. I checked and the certificate was still valid, so I deleted it and installed a new one using auto ssl. However, each time I try and check the certificate I get an error telling me that the certificate is either not installed or unable to read. I have port 443 open in the firewall as well as in the router. If I check the certificate through port 8443 it validates...
What have I done wrong please?

SSL / Re: DNS for your domain dosen't point to this server
« on: October 09, 2019, 07:49:43 PM »

I trolled the server to try and find the reason why I got this message. None of my accounts (domains) had any re-directs or .htaccess settings that would have caused this. Rebuilt webservres, vps and went as far as to completely rebuild Centos 7 and reinstall CWPn and still had this issue.
Sometimes you can't see the woods for the trees.
In my router was set my cctv and as it was using port HTTP 8080 that was a redirect and I was unable to set the SSL certificate... Check the routers guy's

Pages: 1 2 [3] 4 5