I'm getting an object moved error when I try to move any content via Courier.
Clicking the moved to link brings me to a login/password which doesn't go anywhere. Both sites have the same user and login info in the courier.config file. Both sites are on the same server using localhost for testing. The repository.asmx file is in place on both.
The full error text is
Has anyone else encountered this. It feels like I'm probably missing something simple.
do you have any redirects configured on server side (not in Umbraco, but in IIS or the like)? I once saw this error and when i remember correctly it was a misconfiguration the hosting provider made.
I'm using Umbraco 4.11.3 (clean install with mysql) and Courier 2.7.3
I can see the locations and any revison sets. I can also transfer revison sets. I can't however create complete revison sets (they stall out and show the same "moved to" error and never create a compare file. The same as if I try to just directly transfer content (hit deploy and the get the error).
There aren't any server level redirects in place. The page that comes up when I click on the "move to" is generated from Umbraco (id field, password field and a remeber checkbox). If I try filling this out it just goes around in a loop. The form has an action of /login.aspx?ReturnUrl=%2fumbraco%2fplugins%2fcourier%2fwebservices%2frepository.asmx. This happens even if I have the login information in the Courier config.
There's no authentication in place but a reinstall of Courier fixed the initial problem. Now I have a problem with mixed table name cases in the queries Courier uses.
I want to thank you for that input, about a possible network forward/configuration issue.This was exactly what I needed to see to piece together our puzzle.
I ran in to this issue and was having no luck figuring out what changed after an upgrade of Courier. I had configured the Web.Config to forward to https. In courier.config, I was pointing to http and that was causing our error. I changed the URL to https in the config and everything was fixed. It was an easy thing to forget, since only one of the 3 site platforms are available externally (production), usng https. The other couriers are properly configured to point to http.
Object moved
I'm getting an object moved error when I try to move any content via Courier.
Clicking the moved to link brings me to a login/password which doesn't go anywhere. Both sites have the same user and login info in the courier.config file. Both sites are on the same server using localhost for testing. The repository.asmx file is in place on both.
The full error text is
Has anyone else encountered this. It feels like I'm probably missing something simple.Hi Richard and welcome to our :)
What version of Umbraco are you using and what version of Contour?
/Jan
Hi Richard,
do you have any redirects configured on server side (not in Umbraco, but in IIS or the like)?
I once saw this error and when i remember correctly it was a misconfiguration the hosting provider made.
Matthias
I'm using Umbraco 4.11.3 (clean install with mysql) and Courier 2.7.3
I can see the locations and any revison sets. I can also transfer revison sets. I can't however create complete revison sets (they stall out and show the same "moved to" error and never create a compare file. The same as if I try to just directly transfer content (hit deploy and the get the error).
There aren't any server level redirects in place. The page that comes up when I click on the "move to" is generated from Umbraco (id field, password field and a remeber checkbox). If I try filling this out it just goes around in a loop. The form has an action of /login.aspx?ReturnUrl=%2fumbraco%2fplugins%2fcourier%2fwebservices%2frepository.asmx. This happens even if I have the login information in the Courier config.
Thanks
Sounds like you might have some sort of authentication turned on that courier can't get through.
Can you disable it and try again?
There's no authentication in place but a reinstall of Courier fixed the initial problem. Now I have a problem with mixed table name cases in the queries Courier uses.
Matthias,
I want to thank you for that input, about a possible network forward/configuration issue.This was exactly what I needed to see to piece together our puzzle.
I ran in to this issue and was having no luck figuring out what changed after an upgrade of Courier. I had configured the Web.Config to forward to https. In courier.config, I was pointing to http and that was causing our error. I changed the URL to https in the config and everything was fixed. It was an easy thing to forget, since only one of the 3 site platforms are available externally (production), usng https. The other couriers are properly configured to point to http.
So, thanks for that little reminder!
Chris
is working on a reply...