[Errno 10013] error while attempting to bind on address ('::1', 8080, 0, 0): an attempt was made to access a socket in a way forbidden by its access permissions
Hi @Vishal112 ! Welcome to Prodigy 
I need to get more information to help debug this problem. May I know what command you ran when you encountered this error? Can you also try prefixing the same command with PRODIGY_LOGGING=verbose so we can better see what happens?
PRODIGY_LOGGING=verbose prodigy ...
It's possible that there's already a process running in the same port (another Prodigy process, a web app, a Jupyter notebook, etc.) that's why it cannot bind to that specific address. If you're on Linux, you can inspect this by tools such as lsof or netstat (this StackOverflow thread might be relevant).
I am using prodigy in windows 11 machine
python -m prodigy terms.teach demo1 en_core_web_lg --seeds "data,website,internet,issue,cyber"
Initializing with 5 seed terms
internet, cyber, website, issue, data
Starting the web server at http://localhost:8080 ...
Open the app in your browser and start annotating!
ERROR: [Errno 10013] error while attempting to bind on address ('::1', 8080, 0, 0): an attempt was made to access a socket in a way forbidden by its access permissions
and on web browser getting this error
PanelUnLoading(); SetError('Message : No Type Found. StackTrace : at ARCONPAMPlugin.Listener.ListenerCallback(IAsyncResult result)'); PanelUnLoading();
Hello, sir pls reply I had just purchased the prodigy and getting such message , Please reply fast and waiting for your response
ERROR: [Errno 10013] error while attempting to bind on address ('::1', 8080, 0, 0): an attempt was made to access a socket in a way forbidden by its access permissions
please help I am Beginner and just purchased prodigy and getting this error message pls revert back asap
hi @Vishal112,
I noticed that you created a new post for the same issue - please refrain from creating new posts for the same issue.
As mentioned before, it seems like the problem is on your system, most likely due to another process running on the same port or you might not have permission to run anything on that port (e.g., blocked by your firewall).
Did you try the instructions to confirm there is not another process running on the port?
Alternatively, did you try to run Prodigy on a different port? You can do this be prefixing your command as:
PRODIGY_PORT=1234 prodigy ner.manual
Did you also search Prodigy support for your problem as well? From a quick search, there are two posts where other users have reported the same problem (and it was a local port issue):
Started using port at 8081 port no using command set PRODIGY PORT=8081 thanks for sharing
hi @Vishal112!
I'm moving this back to your original as it seems to be related.
The problem is the same but now on the new 8081 port. Could you still be running a prodigy session on port 8081?
netstat -vanp tcp | grep 8081
If so, here's instructions on how to kill that process: