Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOLVED: dns: Failed to bind to port 53 #16

Open
juergenoldbg opened this issue Nov 10, 2022 · 5 comments
Open

SOLVED: dns: Failed to bind to port 53 #16

juergenoldbg opened this issue Nov 10, 2022 · 5 comments

Comments

@juergenoldbg
Copy link

I am trying to get my ipdio mini back to work with your description, that I found here.

I setup the ipdio, as you describe it in Step 1 with a static IP. I restart the ipdio and check, if the device is listed in my network by doing a nmap on my Linux-machine and it is listed.
Then I start the programm, that I downloaded from
https://leo.pfweb.eu/dl/tLoDi for Linux
as root and submit DNS, own IP of the Linux-machine and the location of the patch file.
When I klick start, I get the (error-)message
dns: failed to bind to port 53: Address already in use

When I start the firmwareupdate on the ipdio, I get the message to check my network-settings. I have double-checked, that the 1st dns on the ipdio is pointing to my PC. I guess, this message is due to the 'failed to bind'-message on the PC. I am using Lubuntu 22.04. Any idea, what I could do?

Thanks, Jürgen

@jisotalo
Copy link
Owner

Hi, have you tried googling? Probably you have some other service already listening on port 53 on your PC. That's all I can help, perhaps you should check the results from:

https://www.google.com/search?q=dns%3A+failed+to+bind+to+port+53%3A+Address+already+in+use

@juergenoldbg
Copy link
Author

This was a perfect hint. After I did this changes, the error-message 'Failed to bind ....' didn't show up anymore.
I could now start the server.
Afterwards I started the firmwareupdate on the ipdio and answered with yes. I could see on the screen of my pc, that the configuration of the ipdio was correct as right away some messages appeared in the server-monitor. The last message said something like 'patch-file transferred' and my ipdio said something like 'testing patchfile'
As you suggested I did this five or six times as the ipdio just rebootet after this testing-message. The messages listed on your webpage never appeared.

Do you have any suggestions, how I should continue.

Thanks

@jisotalo
Copy link
Owner

If it says "testing patchfile", you probably have just used the sharpfin-test.patch file. It does not update, just tests the system.

Use the sharpfin-ep2.install file in this repository.

@juergenoldbg
Copy link
Author

Let me just make sure I do understand it correctly. Before I can use sharpfin-ep2.install, I have to install Sharpfin-base_0.3.patch using the 'server'-software.
I did so and I got the sharpfin-website under the IP I choose for the Ipdio. Everything looked fine up until then.
As described on 'https://www.megapico.co.uk/sharpfin/mediaserver.html' I opened the admin-page, selected 'Install addon' and choose
http://www.gforums.de/daten/sharpfin-ep2.install
Something happened on the display of the ipdio, but don't ask what. The radio rebooted and from then on I was not able to http to the IP of my radio anymore. I did a factory reset and started from the beginning with no success. I can ping the radio, but cannot connect.

Thanks for helping

@juergenoldbg
Copy link
Author

I found the solution and now my IPdio Mini works fine (for now, one station). The solution is described here:
#2
and you have to go down quite a bit on the page to a posting by Trashwarez on Oct., 21st, 2021
I'll try more tomorrow

@jisotalo jisotalo changed the title dns: Failed to bind to port 53 SOLVED: dns: Failed to bind to port 53 Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants