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

mDNS_Web_Server.ino: Invalid service type #520

Closed
antonio-fiol opened this issue Jul 17, 2017 · 12 comments
Closed

mDNS_Web_Server.ino: Invalid service type #520

antonio-fiol opened this issue Jul 17, 2017 · 12 comments

Comments

@antonio-fiol
Copy link

mDNS_Web_Server.ino includes the line:
MDNS.addService("http", "tcp", 80);
This causes avahi-browse on Linux to fail with "Invalid service type". Changing that line to the following fixes the issue.
MDNS.addService("_http", "_tcp", 80);

@sansillusion
Copy link

Thanks ! Now I need to know how to get chrome to work with it like my D-link range boosters
ie: open http://lumiere.local
but it does not work.
In ZeroConf Browser for android my D-Links have a extra listing under (_DHNAP) ?
is _DHNAP what's needed and does it exist under esp32 ?

@antonio-fiol
Copy link
Author

@sansillusion as far as I can tell, you do actually not need any service entry for a browser to be able to open said URL. The service entry is only for discoverability.
To set the host name and make it available on the network for mDNS resolution, in the same example file, the line
if (!MDNS.begin("esp32")) {
allows you to find it on esp32.local.
I imagine you already changed that to
if (!MDNS.begin("lumiere")) {

@sansillusion
Copy link

@antonio-fiol Yes I did already changed it.
I kind of got it working by installing Apple Bonjour V3 (extracted from iTunes installer) but it leaves me confused because :
1: My D'Link range extenders did not need Bonjour installed to work
2: It does not work with Edge only in chrome (perfect for me but some people use Edge)

But at least it somwhat works now

@antonio-fiol
Copy link
Author

antonio-fiol commented Aug 29, 2017 via email

@sansillusion
Copy link

@antonio-fiol Thanks a lot, at least it somewhat works now.
I guess the library works with the Bonjour protocol and windows and chrome must have a different implementation of the mDNS protocol.

@me-no-dev
Copy link
Member

new mdns is coming soon ;) it follows all official rules so it should be fine.

@sansillusion
Copy link

@me-no-dev Thank-you for the info !!! You rock !

@copercini
Copy link
Contributor

@sansillusion is it working with the new mdns?

@copercini copercini added awaiting response and removed Status: To be implemented Selected for Development labels Feb 13, 2018
@sansillusion
Copy link

I cant test right now, it works with apple bonjour installed. But I hope it does without having to install apple bonjour like for the esp8266.

I will try later tonight to see and report back.

@sansillusion
Copy link

Still seem the same here, Will not wirk without installing apple Bonjour V3, it does not show up in chrome MDNS browser nor in edge

@sansillusion
Copy link

I seem to have had some weird issue with my setup.
I noticed that even if git GUI sometimes had some updates when doing the update procedures, I had many different files (old versions) than what is shown on GitHub. So I manually downloaded the repo and copied it over my (documets/arduino/hardware/espressif/esp32) folder, than ran get.exe and "$ git submodule update --init --recursive" in git bash and then recompiled my code ( there is a warning about invalid BLE library wich I dont use anyway) and my code jumped from around 30% of program storage to 62% but everything seems to work better even mDNS !!! it shows up in chrome mdns browser plugin YAY !

I guess I will have to cleanup my PC and redo the whole esp32 setup.

@everslick
Copy link
Contributor

This issue is closed, because it looks as if it is not a bug or problem with the ESP32 Arduino core or its support libraries. For general API usage questions or help on specific coding challenges, please visit the arduino-esp32 Gitter channel. If you feel this issue was closed in error, reopen it and comment, why you think this is a bug in the Arduino-Core.

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

5 participants