Apllication Gateway/GoAccess: Invalid URI: The URI scheme is not valid (SAS URL)

After deploying the GoAccess solution to ApplicationGateway, I checked the log:

/var/log/azure/Microsoft.Azure.Networking.ApplicationGateway.LogProcessor/application.log

2019-01-03 17:39:55,941 ERROR [6] ?.? - RefreshBlobs: Caught Exception: System.AggregateException: One or more errors occurred. (One of the query parameters specified in the request URI is not supported.) ---> Microsoft.WindowsAzure.Storage.StorageException: One of the query parameters specified in the request URI is not supported.
at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.ExecuteAsyncInternal[T](RESTCommand`1 cmd, IRetryPolicy policy, OperationContext operationContext, CancellationToken token)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlobContainer.ListBlobsSegmentedAsync(String prefix, Boolean useFlatBlobListing, BlobListingDetails blobListingDetails, Nullable`1 maxResults, BlobContinuationToken currentToken, BlobRequestOptions options, OperationContext operationContext, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Microsoft.Azure.Networking.ApplicationGateway.LogProcessor.LogBlobFetcher.RefreshBlobs(Object state, ElapsedEventArgs e) in E:\src\networkmonitoring\Tools\src\AppGatewayLogProcessor\Services\LogBlobFetcher.cs:line 282

-------------------------------------------------------------------------------------------------------------------

This error refers to the contents of the "blobsasuri.key" file in the same directory. Inside, I've inserted the "Blob service SAS URL", that works fine if copy/paste on browser, listing all containers from my storage account.

What is the correct format for inserting the URI on file "blobsasuri.key"? Could be a bug from ApplicationGateway.LogProcessor?

Thanks!

Start with the error in /var/log/azure/Microsoft.Azure.Networking.ApplicationGateway.LogProcessor/application.log and inspect LogBlobFetcher.cs at line 282. Compare the expected contents of blobsasuri.key with the documented Blob service SAS URL format and trace the ListBlobsSegmentedAsync call. Done means the deployed LogProcessor accepts the configured URI and refreshes blobs without the reported exception.

Written by the indexing model from the issue text.