I’m trying to separate out my Azure environments for local development vs. Dev, Test, Staging, and Production.
For local development I’m using the Azure SDK local storage emulator. To do that you have some connection strings that look like this:
<appSettings> <add key="StorageConnectionString" value="UseDevelopmentStorage=true"/> </appSettings> <connectionStrings> <add name="AzureWebJobsDashboard" connectionString="UseDevelopmentStorage=true" /> <add name="AzureWebJobsStorage" connectionString="UseDevelopmentStorage=true" /> </connectionStrings>
But today I ran into a non-obvious error:
No connection could be made because the target machine actively refused it 127.0.0.1:10002
And found this cool post with the solution in the comment. Basically, the storage emulator turns off after some period of disuse. There’s a handy little batch script in there to clear out the storage and restart it.