Hi, You can see that this issue is about connection timeout and the problem is not theme related. It is all about the hosting provider. He should already recognize and amend this issue by looking at the error message. Please read these related links: https://github.com/anhskohbo/no-captcha/issues/87
This is not a new issue, a lot of users have this problem and it always gets fixed with the help on the hosting provider. We assure that the problem is not on our side.
Sorry but the Problem? Still exsist See Answer from Host Provider (Please translate)
vielen Dank für Ihre E-Mail.
Der Kollege am Telefon hat die Werte für die execution_time und das memory_limit über die .htaccess im Ordner w018e0b7/Masto/ reichlich angehoben. Das memory_limit steht nun auf 512 MB und die execution_time auf 120 s. Das sollte ausreichend sein. Somit scheidet eine serverseitige Beschränkung aus.
An sich besagt die Fehlermeldung, dass der Updateprozess externen Inhalt nicht nachladen kann, weil dieser nicht erreichbar ist. Irgendwann läuft dann der Importprozess in einen timeout.
Wenn der dortige Support davon ausgeht, dass es ein serverseitiges Problem ist, dann sollten die doch auch genauer angeben, was wir tun sollen, damit das Update funktioniert. Gibt es dazu weiterführende Informationen? Weil nur die Aussage es liege am Server hilft weder uns noch Ihnen weiter.
Ist es denkbar, dass die eingestellte PHP-Version 7.2 nicht von dem theme unterstützt wird. Haben Sie schon einmal versucht die PHP-Version auf 7.1 oder 7.0 über das KAS einzustellen und dann das Update auszuführen? Wenn Sie das testen, dann warten Sie nach der Umstellung der PHP-Version immer mal so ca. 10 min bevor Sie das Update ausführen. Einfach damit die Änderung vom Server korrekt übernommen wurde.
Bei weiteren Fragen stehen wir Ihnen gern zur Verfügung.
Mit freundlichen Grüßen Andrea Eberhard Supportteam
Neue Medien Münnich - Inhaber René Münnich - Hauptstraße 68, D-02742 Friedersdorf Ust-ID: DE212657916
The colleague on the phone has increased the execution_time and memory_limit values via the .htaccess in folder w018e0b7 / Masto /. The memory_limit now stands at 512 MB and the execution_time at 120 s. That should be enough. Thus, a server-side restriction is eliminated.
By itself, the error message states that the update process can not reload external content because it can not be reached. Eventually the import process will run into a timeout.
If local support thinks it's a server-side issue, then they should also specify what we should do to make the update work. Is there any further information available? Because only the statement is lying on the server does not help us or you.
Is it conceivable that the adjusted PHP version 7.2 is not supported by the theme. Have you ever tried to set the PHP version to 7.1 or 7.0 via the KAS and then run the update? If you test this, then wait for the conversion of the PHP version always about 10 minutes before you run the update. Just so that the change was taken over correctly by the server.
If you have any further questions, do not hesitate to contact us.
So the Support ask you what can he do ?? If it possible that php Version is wrong ??
Memory Limit and execution_time is been increased please help !
Our theme is fully compatible with PHP >= 7.0 (even with PHP 7.3) - so this cannot be the reason. Increasing the values in php.ini will not fix it either.
The CURL 28 issue is related to the hosting provider, our hands are tied with that problem - unfortunately. All that we can suggest is contact the hosting provider(again) or change the service provider. Thanks
Here you should please contact the manufacturer of the theme.
Gladly we run again a curl directly from the server, for this the manufacturer must provide us a complete line with url. Unfortunately, the complete URL can not be seen in the backend (see screenshot).
If you have any further questions, do not hesitate to contact us.
The Provider ask for complede url so that he can run Update direct from Server
I Need the url for Update to 21.09
Thx
Thank you for your request.
Here you should please contact the manufacturer of the theme.
Gladly we run again a curl directly from the server, for this the manufacturer must provide us a complete line with url. Unfortunately, the complete URL can not be seen in the backend (see screenshot).
If you have any further questions, do not hesitate to contact us.
Sorry Support is solve Problem work together find Solution in this case the betheme Support are sorry Bad what we can do only say Go to the Provider !! An my Provider say only url we can ‚t debug we have Male all Setting !!
Nobody ask me can i lock backend or ftp Session etc. Im disappointed ehr both Support Linie i think the best was is chaning the theme and Provider !!!
Here the last answer from Provider !!!!
we turn around here in a circle. How should we check whether it is a DNS error or a bad connection exists, if we do not know which URL's and domains are concerned. These have not been communicated to date.
This way we can not debug.
The manufacturer of the theme could in this case create a test scenario with which we could run some cURL's for testing. This is not the case. It is always referred only to the fact that it is located at the hoster.
We have already tried it with higher timeout and higher memory limits. Without success.
We are happy to help with the analysis and narrow down the bug, but there should also be some input from the programmer of the software. Otherwise, our hands are tied.
An analysis of the source code by us is not possible. If you can not do without this theme, we regret to inform you that we are probably not the right provider for this theme.
If you have any further questions, do not hesitate to contact us.
Please send us WordPress dashboard access privately thru the contact form which is on the right side at http://themeforest.net/user/muffingroup#contact and we will check what might be the reason.
Notice! Please attach a link to this forum discussion.
Comments
You can see that this issue is about connection timeout and the problem is not theme related. It is all about the hosting provider. He should already recognize and amend this issue by looking at the error message.
Please read these related links:
https://github.com/anhskohbo/no-captcha/issues/87
https://github.com/docksal/docksal/issues/312
https://wordpress.org/support/topic/curl-error-28-operation-timed-out-after-30001-milliseconds-with-0-bytes-receive/
https://toolset.com/forums/topic/update-failed-download-failed-curl-error-28-operation-timed-out-after-300000/
This is not a new issue, a lot of users have this problem and it always gets fixed with the help on the hosting provider. We assure that the problem is not on our side.
thanks
Sorry but the Problem? Still exsist
See Answer from Host Provider (Please translate)
vielen Dank für Ihre E-Mail.
An sich besagt die Fehlermeldung, dass der Updateprozess externen Inhalt nicht nachladen kann, weil dieser nicht erreichbar ist. Irgendwann läuft dann der Importprozess in einen timeout.
Wenn der dortige Support davon ausgeht, dass es ein serverseitiges Problem ist, dann sollten die doch auch genauer angeben, was wir tun sollen, damit das Update funktioniert. Gibt es dazu weiterführende Informationen? Weil nur die Aussage es liege am Server hilft weder uns noch Ihnen weiter.
Ist es denkbar, dass die eingestellte PHP-Version 7.2 nicht von dem theme unterstützt wird. Haben Sie schon einmal versucht die PHP-Version auf 7.1 oder 7.0 über das KAS einzustellen und dann das Update auszuführen? Wenn Sie das testen, dann warten Sie nach der Umstellung der PHP-Version immer mal so ca. 10 min bevor Sie das Update ausführen. Einfach damit die Änderung vom Server korrekt übernommen wurde.
Bei weiteren Fragen stehen wir Ihnen gern zur Verfügung.
Mit freundlichen Grüßen
Andrea Eberhard
Supportteam
Neue Medien Münnich
- Inhaber René Münnich -
Hauptstraße 68, D-02742 Friedersdorf
Ust-ID: DE212657916
//edited
The colleague on the phone has increased the execution_time and memory_limit values via the .htaccess in folder w018e0b7 / Masto /. The memory_limit now stands at 512 MB and the execution_time at 120 s. That should be enough. Thus, a server-side restriction is eliminated.
By itself, the error message states that the update process can not reload external content because it can not be reached. Eventually the import process will run into a timeout.
If local support thinks it's a server-side issue, then they should also specify what we should do to make the update work. Is there any further information available? Because only the statement is lying on the server does not help us or you.
Is it conceivable that the adjusted PHP version 7.2 is not supported by the theme. Have you ever tried to set the PHP version to 7.1 or 7.0 via the KAS and then run the update? If you test this, then wait for the conversion of the PHP version always about 10 minutes before you run the update. Just so that the change was taken over correctly by the server.
If you have any further questions, do not hesitate to contact us.
So the Support ask you what can he do ??
If it possible that php Version is wrong ??
Memory Limit and execution_time is been increased please help !
Thx in advance Dirk
Increasing the values in php.ini will not fix it either.
The CURL 28 issue is related to the hosting provider, our hands are tied with that problem - unfortunately.
All that we can suggest is contact the hosting provider(again) or change the service provider.
Thanks
The Provider ask for complede url so that he can run Update direct from Server
I have only a Part =
http://api.muffingroup.com/theme/download.php?code=…
Thx for Support
See answer from Provider
Thank you for your request.
Here you should please contact the manufacturer of the theme.
Gladly we run again a curl directly from the server, for this the manufacturer must provide us a complete line with url. Unfortunately, the complete URL can not be seen in the backend (see screenshot).
If you have any further questions, do not hesitate to contact us.
The Provider ask for complede url so that he can run Update direct from Server
I Need the url for Update to 21.09
Thx
Thank you for your request.
Here you should please contact the manufacturer of the theme.
Gladly we run again a curl directly from the server, for this the manufacturer must provide us a complete line with url. Unfortunately, the complete URL can not be seen in the backend (see screenshot).
If you have any further questions, do not hesitate to contact us.
Nobody ask me can i lock backend or ftp Session etc. Im disappointed ehr both Support Linie i think the best was is chaning the theme and Provider !!!
Here the last answer from Provider !!!!
we turn around here in a circle. How should we check whether it is a DNS error or a bad connection exists, if we do not know which URL's and domains are concerned. These have not been communicated to date.
This way we can not debug.
The manufacturer of the theme could in this case create a test scenario with which we could run some cURL's for testing. This is not the case. It is always referred only to the fact that it is located at the hoster.
We have already tried it with higher timeout and higher memory limits. Without success.
We are happy to help with the analysis and narrow down the bug, but there should also be some input from the programmer of the software. Otherwise, our hands are tied.
An analysis of the source code by us is not possible. If you can not do without this theme, we regret to inform you that we are probably not the right provider for this theme.
If you have any further questions, do not hesitate to contact us.
Please send us WordPress dashboard access privately thru the contact form which is on the right side at http://themeforest.net/user/muffingroup#contact and we will check what might be the reason.
Notice!
Please attach a link to this forum discussion.
Thanks
It was the problem related to your plugins.
Thanks