I can't log in to speckle manager | error : Failed to listen on prefix 'http://localhost:29363/' because it conflicts with an existing registration on the machine

Help
1

hello ,
I am a new member of the speckle community. I just installed Speckle Manager. however, I have a persisting issue. I can’t log in to the manager.
it gives me this error :
" Failed to listen on prefix ‘http://localhost:29363/’ because it conflicts with an existing registration on the machine."

attached are the logs for reference.

SpeckleCoreLog20230901.txt (190.2 KB)
SpeckleCoreLog20230902.txt (61.5 KB)

2

Hey @Umair_Mohamed welcome to the forum and sorry you’re having issues!

It seems there’s another process using port 29363, are you able to identify it and stop it?
Here’s a guide on how to do so: networking - How do I find out which process is listening on a TCP or UDP port on Windows? - Stack Overflow

I’d also be curious to know what process/app is it, so that we can take the proper measures on our end.

1 Like
3

Hi Matteo, sorry to bring this post back to life but I am facing the same issue with one of my team member’s device.

He gets the same error " Failed to listen on prefix ‘http://localhost:29363/’ because it conflicts with an existing registration on the machine."
Following the link you provided, the process that is on this port is System as you can see in this screenshot

Capture6
Capture6754×100 29.5 KB

Fyi I checked step by step and this port is empty when I close the Speckle Manager. I noticed that the first trial to log in, it opens successfully the browser (without having the error on the port 29363) but when he enters his credentials, he gets this error
" Login failed

Unexpected token ‘’, “”… is not valid JSON"
Note that we got this error on Chrome, on Edge the log in button was unavailable.

Later on when he tried to just log in on Speckle systems he got those errors that I believe are linked to what we tried earlier:
Speckle

Dashboard

Open user menu

MG

Error 500

Failed to fetch dynamically imported module: https://app.speckle.systems/_nuxt/index.xx9oYQMT.js

[Go Home]

Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of “text/html”. Strict MIME type checking is enforced for module scripts per HTML spec.

Could you advise on this issue please ?

4

Hey @Benjamin_TAN, thanks for the detailed report.

Some additional questions:

  • what login type are you using (google / email & password)?
  • can you successfully log in from your browser from https://app.speckle.systems/ ?
  • if not, is there any error message in the dev console of the browser?

Things you can try in the meantime:

  • uninstalling and reinstalling manager
  • restarting your PC
  • trying to log in again
5

@Benjamin_TAN

Hello,

Judging by the error message your browser may be trying to load an old version of our website. Try doing a full cache, cookie & local site data clear for app.speckle.systems.

If that doesn’t work, please provide more context for the error you see in the browser:

  • Post a screenshot of the error page with the reference number, or a screen recording if possible
  • Paste in the reference number from the error page as text
  • If there’s any errors you see in the browser dev tools console or network tab, please share those as well
  • Share the version number of Speckle at the time when the errors occur, you can see it referenced at the bottom of the user menu

image
image381×512 15 KB

1 Like
6

Hello @fabians @teocomi,

We somehow managed to connect his account on the Speckle manager but I frankly have no idea why it was successful since I repeated the same operation again and again until it worked.

Here are the details and videos:

To sum up the steps I was doing at each trial:

  1. Log out from Speckle on all browsers.
  2. Clear the cache for app.speckle.systems
  3. Make sure Speckle manager is closed and not running in the background
  4. Launching the Speckle manager
  5. Login with email & password on browser if not stuck in blank page/issue with buttons
  6. Wait and see if authorization comes and works. Redo all the steps if it didnt work.

Hope this helps

8

@Benjamin_TAN

That is strange. Upon some research I found out that Fireglass seems to be some kind of threat management/antivirus software - could it be that its blocking your access to Speckle?

If I understand correctly, logging in does work now, so maybe the issue is resolved. If not, one thing that could help troubleshoot this further is the Response headers & Response body for those failing asset requests in the Network Tab. That should help us see what comes back in those .js files and the headers might help us find logs to correlate with.

Additionally you could provide us with the value of the x-request-id header that should appear on the request of the page itself (you can use the Doc filter in network tab to find it)

Thanks

9

Indeed the issue is resolved now on our side. If it happens again, I will share you the response headers and body as you requested so that you can troubleshoot the issue.

I don’t have much knowledge in network and cybersecurity so I don’t know if this could be related to this issue but we had one case where we could not connect to a websocket server due to SSL inspection cybersecurity system in our company, this was preventing us to use the associated API.

2 Likes