Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jason Haines 7 posts 77 karma points
    Jan 12, 2017 @ 15:33
    Jason Haines
    0

    Courier setup on Azure

    Hi,

    We have a dev and staging setup on Azure, however we seem to have a problem where they cannot talk to eachother so courier throws an error

    "The request failed with HTTP status 401: Unauthorized."

    the settings in the courier.config are:

    <repository name="Dev" alias="dev" type="CourierWebserviceRepositoryProvider" visible="true">
      <url>https://****dev.azurewebsites.net</url>
      <login>courier</login>
      <password>????</password>
      <passwordEncoding>Clear</passwordEncoding>
    </repository>
    <repository name="Staging" alias="staging" type="CourierWebserviceRepositoryProvider" visible="true">
      <url>https://***staging.azurewebsites.net</url>
      <login>courier</login>
      <password>????</password>
      <passwordEncoding>Clear</passwordEncoding>
    </repository>
    

    Any help would be much apreciated

  • Luke Hook 2 posts 71 karma points
    Jul 05, 2017 @ 14:05
    Luke Hook
    0

    Hi, did you ever find a solution to this? We have a similar set up where we have DEV and STAGING both on azure websites. I can deploy from local but doing so from STAGING or DEV throws a 404 application error. I'm thinking it might be license related perhaps?

Please Sign in or register to post replies

Write your reply to:

Draft