0

enter image description here I got status 401 but two days ago worked fine. Any idea ? How can I fix that?

wroe12
  • 179
  • 1
  • 12
  • Are you logged in in the Cloud Explorer? Can do expand the nodes there to see your Azure resources? – Nikita R. Aug 12 '16 at 21:36
  • I am logged and I see my notification hub but I can't send a message like two day ago. – wroe12 Aug 12 '16 at 21:49
  • Could you go through the guides in [this answer](http://stackoverflow.com/a/38905618/182371) and see if that helps? – Nikita R. Aug 12 '16 at 21:54
  • ; / That answer don't help me. – wroe12 Aug 12 '16 at 22:37
  • I can't use notfication hubs from visal studio with localhost app, the same effect 401 – wroe12 Aug 12 '16 at 23:01
  • Could you provide more details about your set up and what changed over the last couple of days? Also, did you try to restart VS/computer and re-login into the Cloud Explorer? Is there a chance you updated/re-created your hub which resulted in your connection string changing? – Nikita R. Aug 12 '16 at 23:17
  • That is funny because nothing change, I tried reinstall VS but the same effect ; [ – wroe12 Aug 12 '16 at 23:57
  • What's your namespace and hub name? Is it possible that you're on a different network compared to two days ago and some network calls do not get through now? – Nikita R. Aug 13 '16 at 00:07
  • It could be different network because i switch between two network, but I tried on both and the same result. I created new notifi-hub but the same result... – wroe12 Aug 13 '16 at 00:42
  • From a different IP everything works, so Microsoft block my others IP ? – wroe12 Aug 13 '16 at 18:12
  • I don't think it's Microsoft blocking your IP. It's possible that the other network doesn't get all the calls through, firewall settings or some other networking configuration difference. – Nikita R. Aug 15 '16 at 15:56

1 Answers1

0

@wroe12 reported the problem has been solved. Turned out that when the solution worked originally and stopped working later, it occurred on two different networks. It's possible that the difference in those network configurations caused the problem.

Nikita R.
  • 7,245
  • 3
  • 51
  • 62