Closed Boggin closed 1 year ago
Hi @Boggin,
Thank for the feedback. I have not seen a report of this issue before, so I'm hoping you can provide some more details to maybe figure out what's happening:
When you ran the tool in Docker, did the mounting of the volume succeed? (docker run -d -p 8081:80 --mount source=azurenamingtoolvol,target=/app/settings azurenamingtool:latest)
Does the web developer tools console show any errors (F12 in most browsers)
Can you export your configuration and provide in this thread?
Thank you! -Bryan
Hi @BryanSoltis,
Thanks for taking a look.
The mount of the volume succeeded, I can see the /app/settings files when I view the Volume's Data via Docker Desktop.
Opening the dev tools before even loading the web app did yield an error:
[2022-12-12T13:18:44.028Z] Information: Normalizing '_blazor' to 'http://localhost:8081/_blazor'. blazor.server.js:1:37194 [2022-12-12T13:18:44.143Z] Information: WebSocket connected to ws://localhost:8081/_blazor?id=ozIEgxjJyCEeoisMOp9sbA. blazor.server.js:1:37194 The resource at “http://platform.twitter.com/widgets.js” was blocked because content blocking is enabled. localhost:8081 Failed to load script localhost:8081:171:21 onerror http://localhost:8081/:171 (Async: EventHandlerNonNull) loadJs http://localhost:8081/:170 s http://localhost:8081/_framework/blazor.server.js:1 beginInvokeJSFromDotNet http://localhost:8081/_framework/blazor.server.js:1 _invokeClientMethod http://localhost:8081/_framework/blazor.server.js:1 _invokeClientMethod http://localhost:8081/_framework/blazor.server.js:1 _processIncomingData http://localhost:8081/_framework/blazor.server.js:1 onreceive http://localhost:8081/_framework/blazor.server.js:1 onmessage http://localhost:8081/_framework/blazor.server.js:1 (Async: EventHandlerNonNull) connect http://localhost:8081/_framework/blazor.server.js:1 connect http://localhost:8081/_framework/blazor.server.js:1 _startTransport http://localhost:8081/_framework/blazor.server.js:1 _createTransport http://localhost:8081/_framework/blazor.server.js:1 _startInternal http://localhost:8081/_framework/blazor.server.js:1 start http://localhost:8081/_framework/blazor.server.js:1 _startInternal http://localhost:8081/_framework/blazor.server.js:1 _startWithStateTransitions http://localhost:8081/_framework/blazor.server.js:1 start http://localhost:8081/_framework/blazor.server.js:1 er http://localhost:8081/_framework/blazor.server.js:1 Zn http://localhost:8081/_framework/blazor.server.js:1
Thank you for the details. I created a new Docker installation and imported your configuration and everything was fine The error you are seeing int he Web Developer Console is due to it not being able to access Twitter (to load the latest Azure Naming Tool news). You can try disabling this and see if there is still and issue in Generating a name. This should not cause a problem, but would be an easy test top do.
The Generate page will attempt to validate that all the required components are selected before enabling the "Generate" button. It does this by a number of roundtrips to the server to check your fields/form, etc. It appears as if this communication is failing for some reason. Try disabling the "news" feed (screen shot above) and let's see if that fixes it.
If that fails, I recommend trying to deploy to another environment (the provided GitHub Action makes things fairly simple to deploying an Azure App Service).
-Bryan
Turning off 'News' didn't work.
I installed the app to an Azure Web App and I get exactly the same problem, I cannot type into the Instance text box. There's no error in the console.
I've tried in a Firefox private window to make sure no extensions are preventing some script from firing.
I've disabled authentication so anyone can check (this may well be deleted in future): https://azurenamingpulse.azurewebsites.net/generate
Hi Richard,
I just tried exactly how you described and it worked properly. There is no code that would "disable" the Instance field, so I'm not sure why that is happening for you.
I will create a new repository and add you as a contributor. In that repository, I will post a message in the Issues tab to get the URL of your Azure App Service for further investigation.
Bryan,
I've found what may have been the issue and it's not the AzureNamingApp (although the 'Instance' field is the only time this has happened to me).
I have an external keyboard plugged in to a CalDigit TS3 Plus. I tried plugging my keyboard directly into my laptop and then I could type in to the 'Instance' text field. I then plugged the keyboard back in to the CalDigit and it still worked. I don't know what's happened but I don't think it's worth pursuing, either!
Thanks for taking the time to look at the issue with me.
Great news! Yeah, that is definitely a new one to me. I'm glad you were able to figure out and thank you again for the feedback. Please let us know if you have more questions or feedback!
Install of the Docker application as per instructions. Set Admin password, update Configuration of Resource Types and Locations, as advised. Exported base Configuration.
Selecting any combination of options in 'Generate' will not allow typing into the 'Instance' field. The 'Generate' button will remain greyed out (un-clickable). No errors appear in the Console, tested in Firefox, Edge and Chrome. There's no utility in the app without this fundamental.