I have two servers, both of them are blocked from accessing google site kit domain. It used to work correctly, but today suddenly stopped.

Here is the curl command response

$ curl -I https://sitekit.withgoogle.com
HTTP/2 403
content-type: text/html; charset=UTF-8
referrer-policy: no-referrer
content-length: 1579
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000,h3-Q050=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000,quic=":443"; ma=2592000; v="46,43"

however, a telnet request to the host/443 works fine

$ telnet sitekit.withgoogle.com 443
Trying 2a00:1450:4001:827::2011...
Connected to sitekit.withgoogle.com.
Escape character is '^]'.

so clearly I don’t have any connection issue to the server .. it is for some reason blocked from your side

what could be the reason that my servers get blocked?

Thanks for you help and support

Firstly, what is the general opinion of Linode, obviously I’m comfortable in the terminal so I need something with full SSH access. Would the recommendations here of Bluhost or Digital ocean have the level of access. My biggest gripe with a stand alone server is price $30 (I supplied the machine!) and backups. It seems like Linode can start at $5pm with backups for $2pm.

Secondly, what is the best practices to bill clients for hosting after a site build? I’d like to have the client pay for the hosting directly so if we part ways there is not the mess I have incountered in the past 20 years with asking them for the hosting fee each month and not able to automate this (PayPal charges additional fees to run recurring credit card transactions per month under a certain amount of users) Love this WP stuff and I don’t miss Drupal at all

I set up WordPress on Ubuntu 16.04LTS, Apache2, PHP 7.0. Do you have any ideas to set properly on Virtual Private Hosting configuration?

I’ve got a client multisite subdomain install on a Linode. He contacted me to help him because the account was compromised, so I moved everything to a different linode & started over w/a fresh install of the WordPress cor files but an imported database. I did look, & I didn’t see any evidence that the database was compromised. The site url is chrishofstader.com, & that works well. The subsites, though, i.e., blindconfidential.chrishofstader.com, pepper.chrishofstader.com, etc., do not, though I can actually access the site dashboards. Go figure. (WARNING!: the content up there is not for those who are easily offended)!

I believe this was an install prior to WordPress 3.5, as it has a file called blogs.dir under wp-content, so the .htaccess file contains the standard WordPress stuff for a multisite prior to 3.5 (but I tried the .htaccess for 3.5+ also. The wp-config.php is also standard, w/the typical multisite & subdomain install options enabled. I can post everything here if requested, but I fear this post is too long as it is.

Mod_rewrite is enabled on the server, as are wildcard subdomains. There is 1 virtual host file, the domain name.conf, & the main domain is the only site enabled. I did try enabling subsites w/their own configuration file, but that was also ineffective. I’ve renamed the plugins folder, w/similar results. The theme is a default WordPress theme, (twentytwelve, I think) so that likely isn’t an issue. BTW, I can create new subsites, & they work just fine–it’s the old ones that don’t function.

Unless someone has some ideas for me, I may have no choice but to torch this thing & start over. I’d prefer not doing that, as there’s a Piwik install, the data for which the client wishes preserved.

I feel pretty dumb, as though there might be something stupid I’m overlooking, but for the life of me I can’t find it. Maybe a 2nd mind w/a fresh perspective will help.

Thanks for all your hard work, all.

and is this even possible?

I have my website and WordPress installed on a Linode server running Ubuntu.
The directories are:
~/public_html – Website
~/public_blog – WordPress installation

My DNS and site config is set up so that:
hashbang0.com – Points to website in ~/public_html
blog.hashbang0.com – Points to WordPress install in ~/public_blog

Site config as follows:

<VirtualHost 123.456.789.000:80>
     ServerAdmin [email protected]
     ServerName hashbang0.com
     ServerAlias www.hashbang0.com
     DocumentRoot /home/user/public_html/
     ErrorLog /home/user/log/error.log
     CustomLog /home/user/log/access.log combined
</VirtualHost>

<VirtualHost 123.456.789.000:80>
     ServerAdmin [email protected]
     ServerName blog.user.com
     ServerAlias blog.user.com
     DocumentRoot /home/user/public_blog/
     ErrorLog /home/hashbang0/log/blog_error.log
     CustomLog /home/hashbang0/log/blog_access.log combined
</VirtualHost>

Now, I have had enough of tinkering with PHP, HTML, etc. I want to move my WordPress installation so that visitors to hashbang0.com see the WordPress site. At the same time, anyone with links to the old blog.hashbang0.com (most notably RSS links and a few links on StackOverflow, etc.) shouldn’t be cut off.
I’m guessing I could adjust the first part of my site config to:

<VirtualHost 123.456.789.000:80>
     ServerAdmin [email protected]
     ServerName hashbang0.com
     ServerAlias www.hashbang0.com
     DocumentRoot /home/user/public_blog/
     ErrorLog /home/user/log/error.log
     CustomLog /home/user/log/access.log combined
</VirtualHost>

And everything will be well?
Should I look at changing directories or putting some redirect in place for the future? Or would running a small, personal, site like this be OK?

Regards,
Ben