Jagan Krishnaraj

For those who are working with Nginx, this is the example configuration file that worked on the production server.

server {
    if ($host = www.YourName.com) {
        return 301 https://$host$request_uri;
    } 
    if ($host = YourName.com) {
        return 301 https://$host$request_uri;
    } 
    listen 80;
    listen [::]:80;
    server_name YourName.com *.YourName.com;
    if ($http_host ~ "^(.+)\.YourName\.com$"){
        set $http_host_1 $1;
        rewrite ^(.*)$ https://$http_host_1.YourName.com$1 redirect;
    }
}
server {
    listen  443 ssl;
    listen [::]:443 ssl;
    server_name www.YourName.com;
    ssl_certificate /home/ubuntu/.acme.sh/YourName.com/fullchain.cer;
    ssl_certificate_key /home/ubuntu/.acme.sh/YourName.com/YourName.com.key;
    return 301 https://YourName.com$request_uri;
}
server {
    listen  443 ssl;
    listen [::]:443 ssl;
    server_name YourName.com *.YourName.com;
    root /var/www/domains/ROOTFOLDERPATH;
    index index.html index.htm index.php index.nginx-debian.html;
    location / {
     try_files $uri $uri/ /index.php?$args;
    }
    location ~ \.php$ {
     include snippets/fastcgi-php.conf;
        fastcgi_read_timeout            3600s;
        fastcgi_buffer_size             128k;
        fastcgi_buffers                 4 128k;
        fastcgi_param                   SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
   }
    ssl_certificate /home/ubuntu/.acme.sh/YourName.com/fullchain.cer;
    ssl_certificate_key /home/ubuntu/.acme.sh/YourName.com/YourName.com.key;
}

Provided, the default variable on “Additional settings” is set to
$_SERVER[“HTTP_HOST”]

• This reply was modified 3 years, 9 months ago by Jagan Krishnaraj.

Thank you for your response.

I figured it out.

I did a clean Ubuntu 20 installation on an AWS instance.
Installed PHP 7.4 & WordPress 5.7.2
With the default configuration, it didn’t work, however when I updated the option from
$_SERVER[“SERVER_NAME”] to _SERVER[“HTTP_HOST”] it started working right away.

So your plugin supports nginx/1.18.0 server on PHP 7.4 running on ubuntu 20.

This is in the best test-case scenario. To make it work in my actual production environment is going to be a lot of work, but it’s possible.

There is hope.

In your documentation, you can consider include this line
For the Nginx server,
$_SERVER[“HTTP_HOST”] should be the default setting.

Thanks again.
If we get something for free, we should give back too.

You have to put that code in functions.php on the source domain site.

Thank you for the quick response.

I found out about the issue.

Wordpress sets attributes srcset custom attribute that has wrong image URLs, (although src attribute have the right url)

This is sample
<img src="https://responsivecv.com/wp-content/uploads/2020/06/Mobile_Resume_App-min-700x680.png" alt="Mobile Resume app" class="wp-image-1528580" width="350" height="340" srcset="https://qrmobileresume.com/wp-content/uploads/2020/06/Mobile_Resume_App-min-700x680.png 700w, https://qrmobileresume.com/wp-content/uploads/2020/06/Mobile_Resume_App-min-250x243.png 250w, https://qrmobileresume.com/wp-content/uploads/2020/06/Mobile_Resume_App-min-768x746.png 768w, https://qrmobileresume.com/wp-content/uploads/2020/06/Mobile_Resume_App-min-120x117.png 120w, https://qrmobileresume.com/wp-content/uploads/2020/06/Mobile_Resume_App-min.png 800w" sizes="(max-width: 350px) 100vw, 350px">

I disabled the custom attributes with the following function.

function disable_wp_responsive_images() {
	return 1;
}
add_filter('max_srcset_image_width', 'disable_wp_responsive_images');

Then the images started loading fine in the mapped domain.

I believe this issue comes after upgrading to a recent version of WordPress that has a new block editor.

Thank you for your quick support.
Your plugin is very helpful.

• This reply was modified 4 years, 9 months ago by Jagan Krishnaraj.
• This reply was modified 4 years, 9 months ago by Jagan Krishnaraj.

I wish to donate this plugin, Can you add phone number option alone to this plugin?

Yes, it worked perfectly but in a different way.

Your code
if((is_single() || is_page()) && !is_archive() && $is_main_loop)

disables google rich snippets in all the archieve pages, But it’s working fine in default archive pages.

So i did this
if((is_single() || is_page()) && !is_page(342) && $is_main_loop)

this fixed the problem on that page alone leaving behind all other archive pages.

Yes,

I just notice
https://www.livepositiveway.com/inspiring_videos
https://www.livepositiveway.com/inspiring_pictures

also have the ratings but it was done using WordPress default single page for custom post type. Those page doesn’t throw validation error.

But Inspiring Messages is done using custom post template & with custom wp_query.

So is that the problem>

Is there any way to disable the itemprop on archive pages alone?

Some more help

The itemprop attribute was specified, but the element is not a property of any item

Is this error has something to deal with your plugin?

I am getting this error only on this page
https://www.livepositiveway.com/inspiring_messages

and not on any other page all though i use rating system for all pages.

WOW!!!. Replacing all my files with the final zip file in the link specified, fixed all the markup errors in one go.

Thanks a lot.

Your work is Awesome. Thanks for giving this plugin for free & kind enough to reply the support forums. I have 1000 star rating for your plugin.

I got the same problem, I had been resolved this issue with in a couple of days. I wrote my experience here

https://www.theprogrammersguide.com/overcoming-malware-backlisting-by-google/

I hope the information helps.

In my case it was problem with htacess file in my webserver