We are having this strange error. When the keep alive task tries to run, it gives this error: Error while running the 'Keep alive' schedule task. The remote server returned an error: (403) Forbidden.
But when i try to run keep alive manually on the browser via example.com/keepalive/index it runs perfectly.
Our task code:
string url = "https://www.example.com/keepalive/index";
using (var wc = new WebClient())
{
wc.DownloadString(url);
}
We are using NopCommerce 3.70. What are we missing here?
You can check this:
Check your store Url from Admin -> Configuration -> Stores.
Edit your particular store from list and check Store URL might be not same with your browser URL.
Due to this reason you get error like Error while running the 'Keep alive' schedule task. The remote server returned an error: (403) Forbidden.
So please enter correct store URL and restart application.
It will resolved your issue.
Related
I am trying do deploy my website, and i'm using a third party transport to dispatch my emails like : confirmation after subscription and reset password emails.
I am using SendinBlue. I followed Symfony documentation and run composer require symfony/sendinblue-mailer
Then i added MAILER_DSN=sendinblue+smtp://USERNAME:PASSWORD#default in my .env file. Username and password seems correct, i also encoded special characters in my username.
My website is hosted on OVH, i can connect by SSH and run php bin/console messenger:consume async
I have an error message saying : WARNING [messenger] Error thrown while handling message Symfony\Component\Mailer\Messenger\SendEmailMessage. Sending for retry #1 using 1000 ms delay. Error: "Handling "Symfony\Component\Mailer\Messenger\SendEmailMessage" failed: Connection could not be established with host "ssl://smtp-relay.sendinblue.com:587": stream_socket_client(): unable to connect to ssl://smtp-relay.sendinblue.com:587 (Connection refused)"
I also tried to use the SendinBlue API key and got this message : WARNING [messenger] Error thrown while handling message Symfony\Component\Mailer\Messenger\SendEmailMessage. Sending for retry #1 using 1000 ms delay. Error: "Handling "Symfony\Component\Mailer\Messenger\SendEmailMessage" failed: Could not reach the remote Sendinblue server."
I guess i missed something, it's the first time i build a symfony application and im a little lost. I spent all day on this and could not find a solution.
Does anyone have an idea what i did wrong ?
I'm meeting an issue on Meteor with Accounts.forgotPassword method.
My email smtp is well set up as I can use Email.send() without any issue once app is deployed.
But strangely, accounts.forgotPassword return an internal error.
When looking at the logs I have this error :
Exception while invoking method 'forgotPassword' Error: Mail command failed: 550-Requested action not taken: mailbox unavailable
I do not really understand why I would have mailbox unavailable error with Accounts.forgotPassword but not with Email.send()
Does anyone already met that kind of issues ?
I have already searched on the web for any clues but did not find anything :(
FYI I use ionos smtp
Since Email.send is working, I assume your MAIL_URL is set correctly, but your Accounts.emailTemplates is not. From https://docs.meteor.com/api/passwords.html:
In addition to configuring the email package’s MAIL_URL, it is critical that you set proper values (specifically the from address) in Accounts.emailTemplates to ensure proper delivery of e-mails!
I am facing a strange problem when I try to update my remote config value from firebase console and try to publish those changes, I am getting an error A general error occurred.. This problem happens randomly and when I checked my network console for the response I am getting a 500 error.
Following is the JSON response
{
code: 500
message: "Internal error encountered."
status: "INTERNAL"
}
Firebase Remote Config engineer here. We noticed some intermittent issues a few hours ago that we've since resolved. Thanks!
I've just upgraded ROS from 2.7.2 to 3.4.2. And now it becomes interesting. Our users can't open their synced realms because of error.
[RLMSyncManager sharedManager].errorHandler = ^(NSError *error, RLMSyncSession *session) {
LogError(#"RLMSyncManager error %#", error);
if (error.code == RLMSyncErrorClientResetError)
{
[self backupBrokenData];
[RLMSyncSession immediatelyHandleError:error.rlmSync_errorActionToken];
return;
}
};
RLMSyncManager returns Error Domain=io.realm.sync Code=8 "(null)" UserInfo={underlying_error=Error Domain=io.realm.sync.auth Code=3 "(null)" UserInfo={statusCode=400}}
And that's fine seems something with our auth credentials on server. But server log tells me: HTTP response: be33008a-ae5e-4fa1-bab2-f11b40f11b55 {"type":"https://realm.io/docs/object-server/problems/invalid-realm-type","title":"The type of the Realm file was invalid.","status":400,"code":619}
Which is basically You're trying to open partial file with non partial configuration. But client and server uses same full realms. And no modifications happened.
Seems this error returned as false positive.
I've tried to grand administrator permission to that user. It could open his database. But as soon I remove admin permission it sees same error chain.
New users is not affected by this migration issue.
Is there anything I could do to let my users connect to their data?
It appears that issue was caused by bug inside realm-object-server, that was successfully fixed in version 3.4.3.
https://github.com/realm/realm-object-server/issues/374
I get the error as soon as I enter one of my actions on the project.
Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken
Only on 1 page (Action) it happens. The most recent Action I created. The strange thing is that this happens only on the server. Locally on my windows server the page works normally.
The PHP internal logs on the server returns no errors.
The error occurs even if I remove all the code in the action and even if I clear the cache with 'php symfony cc'. Even if I set the permissions with 'php symfony project:permissions'. Even if I combine all of the previous solutions in different order.
Here is the action code:
public function executeExportPostsToProject(sfWebRequest $request)
{
echo 'why?? Show me please!';
}
On the same module there are about 20 other actions decleared the same way. I'm going crazy.
Tryed to check my server configuration for symfony. No Warnings.
The symfony version is 1.4.5.
Seems that the file name of the View is case sensitive under Linux. On Windows hadn't the same problem. On Linux for some reasons with the new files created on windows the problem occured. I renamed the View from exportPostsToProject.php to ExportPostsToProject.php solved this problem.
add route like this in your routing.yml for this action:
route_name:
url: /route-name-example
param: { module: ModuleName, action: exportPostsToProject }
and make sure to be on DEV environment