alex89w
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: After Domain URL change no login to Admin-panel possibleHello,
topic is solved.
I have no clue where the problem was at my WordPress. Something seems to be damaged in the core files or database. I used this WordPress installation over 2 years. Maybe an update in the past went wrong… I have tried many things to repair and also the feedback from the other topic doesn’t helped.
So I installed a secound WordPress at http://www.wanker.wien. Login is much faster there than at my old WordPress.
I have used the build in WordPress export and import to transfer all of the content. Checked all settings page by page and disabled the old WordPress in apache2.Now with the fresh installation it working again.
Hello,
thank you for your tips.
No I’m not using plugin cache or something like that.
I have no clue where the problem was at my WordPress. Something seems to be damaged in the core files or database. I used this WordPress installation over 2 years. Maybe an update in the past went wrong… I have tried many things to repair it but nothing helped.
So I installed a secound WordPress at http://www.wanker.wien. Login is much faster there than at my old WordPress.
I have used the build in WordPress export and import to transfer all of the content. Checked all settings page by page and disabled the old WordPress in apache2.Now with the fresh installation it working again.
Hello,
today I used WP_DEBUG on 22.04 ubuntu server after disable WPS Hide Login” and got this lines:
[27-Jul-2022 18:42:50 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 73 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 89 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 102 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 111 [27-Jul-2022 18:42:50 UTC] PHP Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /usr/share/wordpress/wp-includes/Requests/Transport/cURL.php on line 345 [27-Jul-2022 18:42:51 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 [27-Jul-2022 18:42:51 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 [27-Jul-2022 18:42:51 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 [27-Jul-2022 18:42:51 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 [27-Jul-2022 18:42:51 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91 [27-Jul-2022 18:42:52 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 73 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 89 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 102 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 111 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /usr/share/wordpress/wp-includes/Requests/Transport/cURL.php on line 345 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 [27-Jul-2022 18:42:53 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91 [27-Jul-2022 18:42:54 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:42:54 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /usr/share/wordpress/wp-includes/formatting.php on line 5385 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/wordpress/wp-includes/pluggable.php on line 604 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /usr/share/wordpress/wp-content/plugins/jetpack/functions.compat.php on line 94 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /usr/share/wordpress/wp-content/plugins/jetpack/modules/photon-cdn.php on line 80 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /usr/share/wordpress/wp-content/plugins/jetpack/functions.compat.php on line 94 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /usr/share/wordpress/wp-content/plugins/jetpack/functions.compat.php on line 94 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/wordpress/wp-includes/formatting.php on line 2772 [27-Jul-2022 18:42:54 UTC] PHP Deprecated: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/share/wordpress/wp-includes/formatting.php on line 2772 [27-Jul-2022 18:43:31 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:43:31 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 63 [27-Jul-2022 18:43:31 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 73 [27-Jul-2022 18:43:31 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 89 [27-Jul-2022 18:43:31 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 102 [27-Jul-2022 18:43:31 UTC] PHP Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Cookie/Jar.php on line 111 [27-Jul-2022 18:43:32 UTC] PHP Notice: Error when decoding a theme.json schema for user data. Syntax error in /usr/share/wordpress/wp-includes/class-wp-theme-json-resolver.php on line 330 [27-Jul-2022 18:43:32 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40 [27-Jul-2022 18:43:32 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51 [27-Jul-2022 18:43:32 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68 [27-Jul-2022 18:43:32 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82 [27-Jul-2022 18:43:32 UTC] PHP Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /usr/share/wordpress/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91Hello again,
yesterday I have installed a new ubuntu server 22.04, with apache2, php 8.1, certbot-ssl-certs and mysql. (+ ssl-mod, rewrite-mod etc.)
I transfered all wordpress-files and export+import a sql-dumb to the database. Website is working but I have the same issue like on the old 20.04 server.
When I deactivate “WPS Hide Login”-Plugin, I can’t login again to wp-admin.
So it’s a WordPress topic. Maybe a problem in the database? But how can I figure this out, when WP-debug is logging no issue?
Forum: Fixing WordPress
In reply to: After Domain URL change no login to Admin-panel possibleHello again,
yesterday I have installed a new ubuntu server 22.04, with apache2, php 8.1, certbot-ssl-certs and mysql. (+ ssl-mod, rewrite-mod etc.)
I transfered all wordpress-files and export+import a sql-dumb to the database. Website is working but I have the same issue like on the old 20.04 server.
When I deactivate “WPS Hide Login”-Plugin, I can’t login again to wp-admin.
So it’s a WordPress topic. Maybe a problem in the database? But how can I figure this out, when WP-debug is logging no issue?
Forum: Fixing WordPress
In reply to: After Domain URL change no login to Admin-panel possibleHello,
I have tried also this things but nothing of that helped…
https://bloggingcommerce.com/en/redirect-loop-in-wp-login-with-reauth-1-solutions/Also in debug.log file no specific error.
When I enable “WPS Hide Login” Plugin again, then I can login again.
Has someone an hint how to find the issue?
Thank you.
AlexHello,
I have tried also this things but nothing of that helped…
https://bloggingcommerce.com/en/redirect-loop-in-wp-login-with-reauth-1-solutions/Also in debug.log file no specific error.
When I enable “WPS Hide Login” Plugin again, then I can login again.
Has someone an hint how to find the issue?
Thank you.
AlexHello,
I have tried today some more things:
– Disable all WordPress plugins
– Doing manual WordPress Update with blank wordpress-6.0.1.zip file –> replacing all wp-files.
– Disable all Security-Header entry at Apache2 + at .htaccess file
– Server restart
– Deactivate http –> https redirect (didn’t helped so it’s active again for security reason)Login still not working. Same issue.
Now I’m running out of ideas what I can try next.
When I open a private window (so no stored cookies) and go to https://www.wanker.co.at/wp-login.php
After login, I get to the wp-login page back without error message with this URL:
https://www.wanker.co.at/wp-login.php?redirect_to=https%3A%2F%2Fwww.wanker.co.at%2Fwp-admin%2F&reauth=1When I do this with “Web Developer Tools” of the browser I get at “Network” 3 html files:
– (Status: 302) https://www.wanker.co.at/wp-login.php
– (Status: 302) https://www.wanker.co.at/wp-admin/
– (Status: 200) https://www.wanker.co.at/wp-login.php?redirect_to=https%3A%2F%2Fwww.wanker.co.at%2Fwp-admin%2F&reauth=1And 14 cached scripts and images.
I don’t know if 302 is a problem, because it is HTTP-Statuscode, but I’m using https://
What is also strange when I check the 3. line with Status 200, I have there for example:
Set-Cookie
wordpress_test_cookie=WP%20Cookie%20check; path=/; secureSet-Cookie
wordpress_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-admin
Set-Cookie
wordpress_sec_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-admin
Set-Cookie
wordpress_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-content/plugins
Set-Cookie
wordpress_sec_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-content/plugins
Set-Cookie
wordpress_logged_in_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/
Set-Cookie
wordpress_logged_in_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/
Set-Cookie
wp-settings-0=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/Is this normal that expires= …2021…; Max-Age=0??
Does that mean, that cookies are expires and that’s why login doesn’t work??
Thank you for helping,
Greetings,
AlexForum: Fixing WordPress
In reply to: After Domain URL change no login to Admin-panel possibleHello,
I didn’t got answers from the plugin site.
But today I tried some more things:
– Disable all WordPress plugins
– Doing manual WordPress Update with blank wordpress-6.0.1.zip file –> replacing all wp-files.
– Disable all Security-Header entry at Apache2 + at .htaccess file
– Server restart
– Deactivate http –> https redirect (didn’t helped so it’s active again for security reason)Login still not working. Same issue.
Now I’m running out of ideas what I can try next.
When I open a private window (so no stored cookies) and go to https://www.wanker.co.at/wp-login.php
After login, I get to the wp-login page back without error message with this URL:
https://www.wanker.co.at/wp-login.php?redirect_to=https%3A%2F%2Fwww.wanker.co.at%2Fwp-admin%2F&reauth=1When I do this with “Web Developer Tools” of the browser I get at “Network” 3 html files:
– (Status: 302) https://www.wanker.co.at/wp-login.php
– (Status: 302) https://www.wanker.co.at/wp-admin/
– (Status: 200) https://www.wanker.co.at/wp-login.php?redirect_to=https%3A%2F%2Fwww.wanker.co.at%2Fwp-admin%2F&reauth=1And 14 cached scripts and images.
I don’t know if 302 is a problem, because it is HTTP-Statuscode, but I’m using https://
What is also strange when I check the 3. line with Status 200, I have there for example:
Set-Cookie
wordpress_test_cookie=WP%20Cookie%20check; path=/; secureSet-Cookie wordpress_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-admin Set-Cookie wordpress_sec_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-admin Set-Cookie wordpress_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-content/plugins Set-Cookie wordpress_sec_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/wp-content/plugins Set-Cookie wordpress_logged_in_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/ Set-Cookie wordpress_logged_in_12852b5fa33dca83da6e3ea2dbe355fd=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/ Set-Cookie wp-settings-0=%20; expires=Fri, 23-Jul-2021 12:45:35 GMT; Max-Age=0; path=/Is this normal that expires= …2021…; Max-Age=0??
Does that mean, that cookies are expires and that’s why login doesn’t work??
Thank you for helping,
Greetings,
AlexForum: Fixing WordPress
In reply to: After Domain URL change no login to Admin-panel possibleHi Threadi,
thank you for this hint.I have disabled every Plugin one by one. I had a issue at the Plugin WPS Hide Login where I set a custom login URL. After disable I was not logout automatically. (But by changing the URL of WordPress you get logout automatically.)
So I logout manually, get to the default login URL and then I have the same issue. Luckily I was still logged in on a second device and could activate the plugin again. Now login is working again…Looks like this plugin is the problem. So I have created a new topic for this plugin (https://ww.wp.xz.cn/support/topic/after-disable-wps-hide-login-and-logout-login-redirect-loop/).
When login is working without this plugin, I will try again changing the URL of WordPress.
I will let you know.
Thank you for helping.
Greetings,
AlexForum: Plugins
In reply to: [JetBackup - Backup, Restore & Migrate] Scheduled Backup failed every timeGood morning,
What I did:
– BackupGuard Setting –> “Numbers of rows to backup at once” from 10000 to 1000
– wp-config.php at the end of the file –> set_time_limit(300);
– Restart apache2Scheduled Backup from 2021-05-20 05:22:00 failed again.
Maybe my wp-config change didn’t worked. Should I try it with .htaccess?
Here is the backuplog file from last failed backup:
https://we.tl/t-HlXuZnaNSRThank you for your help
Forum: Plugins
In reply to: [JetBackup - Backup, Restore & Migrate] Scheduled Backup failed every timeHello again,
I have googled it. 🙂
According to this website I have searched in all 3 files.
At the moment only in my php.ini file I found “max_execution_time = 30”
https://thimpress.com/knowledge-base/how-to-increase-maximum-execution-time-for-wordpress-site/The question is if I should change it here in the php.ini or would it better for the future to set for example “set_time_limit(300);” in wp-config.php file?
Because when I will upgrade the php-version in the future then maybe the php.ini file can change?!? So I think it would be better in the wp-config.php file.
Which value would be great for execution time?
Thank you very much
Forum: Plugins
In reply to: [JetBackup - Backup, Restore & Migrate] Scheduled Backup failed every timeHello,
I have set “Numbers of rows to backup at once” from 10000 to 1000.
But what do you mean with “…increase the Max Execution Time from your hosting”?
Do you mean the setting “Request frequency” at backupGoard? This is set with “10 seconds”.Thanks,
greetings,
AlexForum: Plugins
In reply to: [JetBackup - Backup, Restore & Migrate] Scheduled Backup failed every timeHi again,
here is a backup-log from a successful backup that I have started manually:
https://we.tl/t-zmQoVQX7pAForum: Plugins
In reply to: [JetBackup - Backup, Restore & Migrate] Scheduled Backup failed every timeHi,
thank you for your help.
Yes, it’s always failing at the scheduled backup.
Manual backup are successful.Here you can find the backup-log for the failed backup:
https://we.tl/t-rGuwPGVbpO