Changed the general settings of my wordpress website: "WordPress Address (URL)" and "Site Address (URL)" to www.wikipickr.com. After saving when I opened my website the https in url was crossed clicked on it and then details and this was displayed.
Problem Screenshot
What I wanted: I wanted the green padlock to appear before the url which meant that the connection is encrypted. And I wanted visitors to stay on www.wikipickr.com domain not the 000webhost domain I mentioned below, as before changing the setting, they were being redirected to wikipickr.000webhost.com.
Things you might need to know: I own www.wikipickr.com from Go Daddy. I'm actually hosting my website on a free hosting provider, 000webhost. My URL for that site is [wikipickr.000webhostapp.com][3] . I added a CNAME record in
my Go Daddy DNS setting to wikipickr.000webhostapp.com and then When I changed the setting from /wp-admin as I mentioned above, The cross mark started appearing. This is my first time hosting a website, feel free to bash me for my stupidity, if any. Thankyou for reading all this.
The link you provided now has data base error can not connect you need to follow the instructions provided by godaddy if that is where you purchased your certificate
After you've verified your certificate request, you can download your certificate files, and then install them on your server.
Install SSL certificates
Related
I have a static Gatsby site that uses WordPress for it's back end. I also have the WordFence plugin installed to prevent hackers from causing havoc. I started out without WordFence installed, the site got hacked, and we had to scrap the whole back end and start over with a new database.
When trying to deploy my Gatsby website using Netlify I recieve this error message:
If you are using a security plugin like WordFence or a server firewall you may need to whitelist your IP address or adjust your firewall settings for your GraphQL endpoint.
I have the NetlifyPress WordPress plugin installed. It doesn't help prevent the issue.
I was able to fix this error locally by whitelisting my IP address in the Wordfence firewall settings.
It's not as simple whitelisting the Netlify automated build processes on the website though.
Does anyone know how to stop Wordfence from from blocking Netlify?
I figured it out!
Go to WordFence dashboard.
Click on "Tools" to view a live graph of intercepted suspicious activity
Switch to Netlify and run a deploy of your site (it should fail)
Go back to the WordFence graph and take a look at the top row, the "page visited" column should have "/graphql" in it
Click on that row
Click on the "Add Param to Firewall Allowlist" button
Run your Netlify build again and it should work!
Some caveats:
Be super careful that you don't accidentally whitelist a hacker!
WordFence is constantly blocking attacks. Most attacks aren't trying to access "/graphql" though, so that is a pretty good indicator of which rows are services you want to white list and which rows are hackers that need to stay blocked.
The above method seems to give access to anyone that is trying to access the "/graphql" endpoint. That might be considered a security issue for you. On the plus side, it meant that it also fixed my BitBucket pipeline issue.
An alternative method is to copy the IP Address in the "IP Address" column then add it to your IP Address whitelist.
Go to the Wordfence dashboard
Click "Firewall" in the left nav bar
Click "All firewall options"
Enter the IP address in the "Allow listed IP addresses that bypass all rules" field
That could turn into quite a long list though as Netlify has a lot of servers all with different IP addresses. You will have to be constantly whitelisting new IP Addresses. It is admittedly a much more secure method than the first option though. This method ensures that only Netlify will have access to the "/graphql" end point.
The goal is to have free ssl from cloudflare. So I moved dns records to cloudflare and is showing me - Certificate is Active. When I go to 'Analytics tab' it shows me traffic that is coming to the website. But when I enter the site https://www.zampadebattista.com I'm getting 'Your connection is not private'. It look that virtualmin is using his own self-signed certificate that I didn't setup. Do I need change something in virtualmin?
Thanks for your help
Try to see if the same key and Certificate that is in the Directory is the same as the CloudFlare.
Clean Your Cookies ...
Enter the site with the Browser in Anonimo
Here it is working perfectly!
If you have solved, clarify the solution you found ...
I've recently hosted my wordpress website through AWS Lightsail. The site has a contact form and a newsletter, but neither are working. I'm also unable to send a password reset email through wordpress, receiving a message that the host may have disabled the mail() function.
How do I setup email on my website? Is it handled through the domain or the host? I've read that I may need to sign up for AWS SES, however I'm unsure how to proceed. My client has also informed me that they have Outlook 365 setup for the domain, but I'm unsure where that fits in.
Apologies for the vagueness. I'm new to hosting websites online, and have been unable to find any useful tutorials/resources so any help would be greatly appreciated.
I would suggest not hosting your client's email through your Lightsail server. There are a lot of extra headaches to consider and there are other services that are more reliable and offer a better more robust user interface than the options available on server.
To get your client a custom domainname email address (ie joe#domainname.com) here are two options:
Zoho -
Cost: FREE
You can sign up here: https://www.zoho.com/workplace/pricing.html?src=zmail
You need to verify the domain name for this to work (either by adding an HTML file to the site or a CNAME to the domain)
GSuite by Google - Cost: $5/user/month
You can sign up here: https://inbox.google.com/u/0/search/google%20suite#m_-1052842142248281614_
You can also get some good promotional codes to get 20% off the first year - here's one: 9746YLRVNWERPAH
And, to your question about making sure forgot password emails are sent, make sure sendmail is installed on the server (apt-get install sendmail), that the /etc/hosts file contains the following
127.0.0.1 localhost localhost.localdomain yourhostnamehere
and that port 25 is open on the server.
I have a wordpress site:
http://www.fairlady-sleepingtiger.co.uk/
but the home page is not displaying all the content.
When I inspect the Console I see this message:
www.fairlady-sleepingtiger.co.uk/:12 A Parser-blocking, cross-origin script, http://ajax.cloudflare.com/cdn-cgi/nexp/dok3v=088620b277/cloudflare.min.js, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity.
I have deleted/disbaled all Cloudflare functionality from this site but this still comes up.
Can anyone help please?
You are still pointing to Cloudflare nameservers, so your domain is still being proxied.
There is a period of time where we will continue to handle DNS even after you remove your zone, which protects against this situation where the nameservers didn't get changed. Otherwise the site would just be unreachable.
If you want to completely remove Cloudflare you need to update the nameservers at your registrar, and depending on the registrar it should update in 24 hours or so.
I have a client that has a domain registered through GoDaddy (e.g., http://www.godaddysite.com). He has the domain set to forward w/masking to a page on our servers (eg., https://www.someuniversity.edu/someproject/loginpage.aspx).
When on our network (a university network) I can navigate to his domain, the forwarding/masking works and I can log in without issue. However, anyone off the university network, when visiting the client's site, cannot log into the site. It forwards/masks as it should, accepts the user name and password but stays on the login page after the credentials are accepted. If they navigate directly to my site they have no issues.
I checked his GoDaddy settings and everything appears right. GoDaddy says it is our configuration that is causing the problem (not allowing a different domain mask the site). Is this true? Is there something I need to change in IIS to allow people to log in when they visit through the GoDaddy site?
Update:
Finally was able to test this offsite. This scenario ONLY happens in IE. So now it is a browser setting issue.
The most common cause of this sort of problem is described here: http://blogs.msdn.com/b/ieinternals/archive/2013/09/17/simple-introduction-to-p3p-cookie-blocking-frame.aspx
If you change the IE Privacy Settings (Tools > Internet Options > Privacy) to Accept All Cookies does the problem go away? If so, then you need to set a P3P response header.