[email protected]
Forum Replies Created
-
He Peter, Looks like its something different. This is what I’m seeing in debug log :
I have no clue why cloudfront is involved here. So some how when Wordfence is detecting an admin login and mail is send via Fluentsmtp plugin its get hold of by cloudfront. Any suggestions
[03-Aug-2024 16:56:40 UTC] wfCentralAPIException: HTTP 403 received from Wordfence Central:
ERROR: The request could not be satisfied 403 ERROR The request could not be satisfied.
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: rSaSV7aCvVtGZBUZB5A6HzsaApt_4c262jTQlENhvrze4JpstrzkRw==
in /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php:309
Stack trace: 0 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(264): wfCentralAuthenticatedAPIRequest->fetchToken() 1 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(62): wfCentralAuthenticatedAPIRequest->getToken() 2 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(586): wfCentralAPIRequest->execute() 3 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(2600): wfCentral::updateScanStatus() 4 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(188): wfScanEngine::startScan() 5 /home/deb10069/public_html/wp-includes/class-wp-hook.php(324): wordfence::hourlyCron() 6 /home/deb10069/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 7 /home/deb10069/public_html/wp-includes/plugin.php(565): WP_Hook->do_action() 8 /home/deb10069/public_html/wp-cron.php(191): do_action_ref_array() 9 {main}
[03-Aug-2024 16:56:40 UTC] wfCentralAPIException: HTTP 403 received from Wordfence Central:
ERROR: The request could not be satisfied 403 ERROR The request could not be satisfied.
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: cgFB4PMX9QcGS9B00DbzZDUjXNwDb3U26i0PtPgqR8KV23aH-0yMzA==
in /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php:309
Stack trace: 0 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(264): wfCentralAuthenticatedAPIRequest->fetchToken() 1 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(62): wfCentralAuthenticatedAPIRequest->getToken() 2 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(517): wfCentralAPIRequest->execute() 3 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfIssues.php(395): wfCentral::deleteIssueTypes() 4 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(202): wfIssues->deleteNew() 5 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(1951): wfScanEngine->deleteNewIssues() 6 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(460): wfScanEngine->scan_oldVersions_finish() 7 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(221): wfScanEngine->doScan() 8 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScan.php(211): wfScanEngine->go() 9 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(1517): wfScan::wfScanMain() 10 /home/deb10069/public_html/wp-includes/class-wp-hook.php(324): wordfence::ajax_doScan_callback() 11 /home/deb10069/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 12 /home/deb10069/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 13 /home/deb10069/public_html/wp-admin/admin-ajax.php(207): do_action() 14 {main}
[03-Aug-2024 16:56:41 UTC] wfCentralAPIException: HTTP 403 received from Wordfence Central:
ERROR: The request could not be satisfied 403 ERROR The request could not be satisfied.
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: vBvIfQ0rH7E_wIXga8d_fKRYPXcPY7vgSXwhjApCEhT5GOCU-6w6lg==
in /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php:309
Stack trace: 0 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(264): wfCentralAuthenticatedAPIRequest->fetchToken() 1 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(62): wfCentralAuthenticatedAPIRequest->getToken() 2 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(586): wfCentralAPIRequest->execute() 3 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScanEngine.php(238): wfCentral::updateScanStatus() 4 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScan.php(211): wfScanEngine->go() 5 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(1517): wfScan::wfScanMain() 6 /home/deb10069/public_html/wp-includes/class-wp-hook.php(324): wordfence::ajax_doScan_callback() 7 /home/deb10069/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 8 /home/deb10069/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 9 /home/deb10069/public_html/wp-admin/admin-ajax.php(207): do_action() 10 {main}
[03-Aug-2024 16:56:42 UTC] wfCentralAPIException: HTTP 403 received from Wordfence Central:
ERROR: The request could not be satisfied 403 ERROR The request could not be satisfied.
Request blocked.
We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront) Request ID: eq-Gb5WKCIe98Jh-Xh8v6kAP_Kvu4f2fCq8R8gpQ3PaUFyhJi17L7g==
in /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php:309
Stack trace: 0 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(264): wfCentralAuthenticatedAPIRequest->fetchToken() 1 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(62): wfCentralAuthenticatedAPIRequest->getToken() 2 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfCentralAPI.php(586): wfCentralAPIRequest->execute() 3 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfUtils.php(1477): wfCentral::updateScanStatus() 4 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wfScan.php(322): wfUtils::clearScanLock() 5 /home/deb10069/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(1517): wfScan::wfScanMain() 6 /home/deb10069/public_html/wp-includes/class-wp-hook.php(324): wordfence::ajax_doScan_callback() 7 /home/deb10069/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 8 /home/deb10069/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 9 /home/deb10069/public_html/wp-admin/admin-ajax.php(207): do_action() 10 {main}
[03-Aug-2024 16:58:51 UTC] PHP Deprecated: Optional parameter $post_types declared before required parameter $location is implicitly treated as a required parameter in /home/deb10069/public_html/wp-content/plugins/monarch/monarch.php on line 3783
[03-Aug-2024 16:58:53 UTC] …/builder/core.php:5382 et_builder_get_google_fonts():
An unkown error has occured while trying to retrieve the fonts from the Google Fonts API. Please ensure your Google API Key is valid and active.He Peter thanks for your reply. Looks like Wordfence is in learning mode and sofar I can see nothing is blacklisted. As which user is Wordfence trying to to send the alerts ? I know I can set the TO user. But I did not notice a place where I can define the from user. See using Fluenthsmtp to send message via Office 365 requires a correct user in Office 365 to be used as from.
Greets
Coen
You can close this Question I figured way to go.
Anca you can skip this .. Looks like I had disable dynamic translation check that was the issue
Anca, Looks like divi supreme has fixed the issue. But as always I’m running from one to the next. Looks like that for some reason translate press is changing behavior on translation. From string to block .. This messed up a big bunch of my translations on a page If I switch from block to string I see my translations as a block transalation is not showing up .. Look like block translation is set to a default. Is this new ?
Anca thank you for the update will forward your info to DIVI Supreme
Greets
Coen
Anca,
I’m stupid I could have used onedrive … please see file in url with png’s
I checked that option / clear cache and history on Browser .. I does not resolve the issue
Greets
Coen
P.S I have 2 images from Divi supreme which show the correct and wrong path .. Is there a way to get you those PNG
Btw I’m using Divi not Elementor 🙂
Just switch from English to Dutch and you will see that Lotty module not showing probably caused by a wrong URL (That us what Divi Supreme Support team told me)
He Anca
Basically it happens on Lottie annimations added with Divi Supreme Lottie file module on page
Our Portfolio | Quant-ICT-DEV . Let me activate the translatepress again.
Greets
Coen
Is there a way to upload some picture of the issue
Hi , FYI I’m not using any other portfolio links that translate press. I’m using DIVI from elegant themes. Each module has a position to place a link .. (Example for a BUTTON or Blurb Image or when using a gallery for each Image ). Regular menu navigation seem to be working. And Some time the link works and keeps the current language. Its a random thing that the language jumps back to default. You can hit the link in a button of on a image 2-3 time and it switches nice keeping language and then out of the blue it switches back.
Is there anyone with a feedback on my issues
even with Force language in custom links from TP Settings –> General tab, as well as absolute paths for these custom links The language returns into default language after some moves.
I did a short test with Gtranslate which had no issue at all switching around languages . True should use a paid version to get manual translations for certain things . .. True not ideal and not locally managed .. So what can I do to make translate press to work properly