Publish to “Medium” creating a server over load.

Hello,

Thank you so much for reaching out and thanks for describing your request.

An overload or lack of server capacity can cause the social media settings widget in the “Social Media Scheduling & Sharing” overview to load very slowly or not load at all.

If your website is hosted on a server with low server capacity, you can turn on the Blog2Social Legacy Mode to reduce server load.

In Legacy Mode, the plugin will load contents one after the other (asynchronous loading) instead of loading all at once. Some web hosting services also limit the number of outgoing connections. In this case, the Legacy Mode makes sure that connections to your social media accounts are loaded successively.

To activate Legacy Mode, go to “Blog2Social -> Settings -> General -> System” and tick the box saying “activate Legacy Mode”.

Despite this, the “MEDIUM BOT FETCH” you mentioned seems to be an automatic process that is performed in order to publish your content via the Medium platform (API).

Please be so kind as to enable this option and retest the sharing process once again afterward.

However, please note that the Medium rules for publishing are very rigid. If you share too many posts in too short a time, Medium is likely to suspend your account. Please follow the Medium community rules very closely.

Blog2Social provides a special editor for Medium, so have any option to adapt your content to meet the Medium rules.

Feel free to let me know if the suggested solution resolved your request, or if you require further assistance regarding this matter.

I’m looking forward to your reply.

I tried the legacy mode, (i was a premium costumer in the past)
It’s not connected to legacy mode.

The problem when MEDIUM social media got publish (1 post of one page)
medium.com scans all the pages of your website! (in legacy mode as well).

Medium.com shot a “BOT” with your plugin and scan all the website in one shot.
My website have 110 pages.
When MEDIUM BOT do it, i get overload (with legacy mode and without)

I’m waiting the daily limit of Medium will pass (this because i tried so many times to understand from where it’s come from).

When the limit will go away, i will send you the traffic log from NGINX.
And you will see MEDIUM BOT FETCH (something like that)
get inside ALL THE PAGES ON YOUR WEBSITE IN ONE SHOT!.

I have 110 pages!
In one shot, the bot get to all the 110 pages, this cause overload.
(My website is like 20 websites, it’s very, very big with a lot of pages)

I test it for a couple of days.
When i turn off the publishing to MEDIUM, i not get overloaded.
(in legacy mode and without)

This is a screenshot from NGINX log, right after publishing with your plugin:
https://ibb.co/C0q9DPR

Look the: Mediumbot-MetaTagFetcher/0.3

I have another server with website in English (locksmithunit.com)

Your plugin do the same thing on the other server as well ??

When you not publish to MEDIUM social media, this overload not happens.
(You can see on the screenshot the overload as well – 6CPU, i have only 2CPU)

Hello Nadav,

Thank you for your reply and this feedback.

Since Blog2Social uses the official Medium.com API to authenticate a connection and publish your content, there is no direct connection between the behavior you described and the API functionality or any other feature of Blog2Social.

External bot crawl processes are out of scope of Blog2Social. However, if a bot crawl is causing a time-out, it has most likely something to do with the available server capacity.

Please take a look at the page speed checker for your website: locksmithunit.com
https://pagespeed.web.dev/report?url=https%3A%2F%2Flocksmithunit.com%2F.

So far, no other Blog2Social user faced such a behavior, therefore it sounds like there is some specific environment on your website that is causing this behavior.

Is there any issue when sharing content on other social media networks with Blog2Social?

Has there been any change on your website environments recently? Or which other tools or plugins have been enabled/configured on both of your servers since you noticed this behavior for the first time?

As a workaround, you could try to identify the “Medium Bot fetch” IP and block it from accessing your server, in order to try detecting if you still can publish content on Medium.

We also recommend to check your websites with the page speed tool to see if you can optimize your page load.

Feel free to let me know if the suggested solution resolved your request, or if you require further assistance regarding this matter.

I’m looking forward to your reply.

If you check my website with page speed, you will see it’s insane (if you’re in U.S = locksmithunit.com)

If you look here in Europe:
locksmithunit.es

Your plugin triggers a crawl from “medium.com” on all the pages, (even if you publish one time, one page).

medium.com will crawl all your website.

On the other hand, all the other social media scan only the page got published (1 page)

Your plugin triggers crawl from medium.com , exactly after publishing with blog2social.

Now, as i said, i have a website of 119 pages…
To scan 120 pages with a bot, can cause overload.

If you have a website with 10 pages, ok.

But i have 120 pages, It’s like 12 websites with your plugin, in the same time.

• This reply was modified 2 years, 6 months ago by Nadav Levi.

Hello Nadav,

Thank you for your reply and this additional feedback.

Bot crawl processes are out of scope of Blog2Social and its service.

Since Blog2Social uses the official Medium.com API to authenticate a connection and publish your content, there is no direct connection between the behavior you described and the API functionality or any other feature of Blog2Social.

Please note that this issue is unique and uncommon. It is most likely connected with a specific setting in your website environment.

However, as suggested you could block the requests of the “Medium Bot fetch” IP as a workaround to prevent a server overload.