I am currently experiencing the same problem. The error pops up as soon as I open the courier dialog, before I ever get to choose a destination. I don't get the error on localhost however, and deploying content works fine to our online environment.
Umbraco version: 7.5.9 assembly: 1.0.6247.17495
Courier version: 3.0.4
Were you able to fix it? And if so, can you share your insights?
Thanks René for coming back here and posting your solution.
For me that was not the problem however, all environments were synched and running the exact same code, including plugins.
I was able to fix it just now. We are running our servers on Azure. We are also protecting our /umbraco page on production, and our entire acceptance enviroment via basic ip whitelisting.
Courier of course needs to be whitelisted to these urls. This means adding the app-service outbound ip's to the whitelisting of the other environment.
But it also appears the ip's need to be added to their own whitelist, probably because Courier is making network calls to itself, similar to the auto publish/unpublish feature (which was broken before but now also works again).
HTTP status 403 - Courier
Hi
Umbraco version 7.4.3 assembly: 1.0.5948.18141
Umbraco Courier 2.52.4
I have a setup where i have: local, stage, and live servers.
I´m only able to tranfer from local to stage and local to live
If i try to tranfer from
René
Hi René,
I am currently experiencing the same problem. The error pops up as soon as I open the courier dialog, before I ever get to choose a destination. I don't get the error on localhost however, and deploying content works fine to our online environment.
Umbraco version: 7.5.9 assembly: 1.0.6247.17495
Courier version: 3.0.4
Were you able to fix it? And if so, can you share your insights?
Thank you, Hugo
Hi Hugo
As i remember there was a differet version of courier on my live server.
Try to check umbraco version and courier version, it must be the same.
René
Thanks René for coming back here and posting your solution.
For me that was not the problem however, all environments were synched and running the exact same code, including plugins.
I was able to fix it just now. We are running our servers on Azure. We are also protecting our /umbraco page on production, and our entire acceptance enviroment via basic ip whitelisting.
Courier of course needs to be whitelisted to these urls. This means adding the app-service outbound ip's to the whitelisting of the other environment.
But it also appears the ip's need to be added to their own whitelist, probably because Courier is making network calls to itself, similar to the auto publish/unpublish feature (which was broken before but now also works again).
Hugo
is working on a reply...