#How to debug go2rtc

1 messages · Page 1 of 1 (latest)

undone temple
#

Hey all, I need to get access to the debug console of go2rtc to get data for a bug ticket, but I can't figure it out. I've got

default_config:
  
go2rtc:
    debug_ui: true

in my configuration.yaml, and if I understand the documentation on the home asssistant website correctly, that should give me a debug UI on http://homeassistant:11984 but I don't get anything.

What am I doing wrong here? Can somebody help me out?

cinder palm
#

What URL do you use to connect to the HA frontend?

#

And maybe elaborate on 'don't get anything'

undone temple
#

If I want to connect to ha frontend, I navigate to http://homeassistant:8123. By "I don't get anything" I mean that in the browser I get a refused connection, and when I nmap the server, it shows the port as closed.

#

Port 18555 seems open, but it doesn't accept connections either.

violet vector
#

Did you restart HA after editing the config?

undone temple
#

Yes I did. I can try again if you would like me to.

#

So my assumption that a web ui should exist on port 11984, and what I put into the config file are basically correct then?

#

I've restarted again and the situation hasn't changed.

violet vector
#

You're using HAOS then?

undone temple
#

Yes I do.

#

Should I try restarting the OS then?

violet vector
#

I doubt that would be necessary

#

But feel free to try

undone temple
#

That was my assumption also, but I guess it can't hurt to try.

#

Ok, server has rebooted, and the situation is basically the same.

cinder palm
#

I already had it enabled in my container install and it works for me:

violet vector
#

What if you use the HA IP address instead of homeassistant host name? The default URL is http://homeassistant.local:8123/, not sure if you have something else going on there.

#

I'm not an HAOS user, but I have a VM for testing. I just started it, configured go2rtc the same way and after a restart the UI is available.

undone temple
undone temple
violet vector
#

Depends on what homeassistant is resolving to.

undone temple
#

🤷‍♂️ It's really just mDNS. There's no CNAME or anything involved really.

violet vector
#

Ok, wasn't sure since it's not the default.

undone temple
#

How is it not the default? As far as I know, it is. I sure didn't fiddle with it.

violet vector
#

http://homeassistant.local:8123/ is the default AFAIK

#

That's what my instance comes up with and is in the docs.

#

So just wasn't sure if you had something else configured in your setup.

undone temple
#

the .local postfix is basically just an optional clarification in case you have an external search domain set.

#

If your search domain were set to mydomain.com and you had a server homeassistant.mydomain.com, you'd need it, but as long as you don't have a server of the same name in your search path, it's optional.

violet vector
#

Not the case for my PC, but ok.

#

Doesn't seem to be the issue anyways.

undone temple
#

Definitely not.

#

Is there any way I can remove and reinstall go2rtc? Something seems to have gone wrong with it at some point.

violet vector
#

It's included in the HA container, not really anything to install

undone temple
#

Well, it seems to be running in principle, otherwise the 11855 port would not be open.

#

It's just not behaving the way it should.

violet vector
#

All the debug_ui settings does is configure go2rtc to listen on all ip addresses

undone temple
#

Which may very well be the root cause of my problem

#

maybe the internal routing of the container is snoggered?

violet vector
#
➜  / docker exec -it 523f77a0a5f7 sh -c "cat /tmp/go2rtc*"  
# This file is managed by Home Assistant
# Do not edit it manually

api:
  listen: ":11984"

rtsp:
  listen: "127.0.0.1:18554"

webrtc:
  listen: ":18555/tcp"
  ice_servers: []
undone temple
#

can't really do that on haos, can I?

violet vector
#

I did that from the community ssh addon

#

the HA container uses host networking

#

Also I can type login from the console to get to a shell, and ss -nltp shows it listening

undone temple
#

I actually have that addon installed, but I thought it places me inside the container? It doesn't seem to know the docker command

violet vector
#

Protected mode must be turned off to use docker

undone temple
#

How do I do that?

violet vector
#

go to the add-ons settings and turn it off

undone temple
#

Hm, It would appear the ssh port on my ha server isn't open...

violet vector
#

it's usually not

undone temple
#

Also it says port 22 is deactivated in the addon settings.

violet vector
#

it would not be enabled unless you configured the add-on for it

undone temple
#

It seems I don't quite follow what you are doing here. Are you using the web console or an ssh client to connect?

violet vector
#

I used the host console

undone temple
#

Oh you connected a monitor and a keyboard!

violet vector
#

technically, yes. it's a VM.

undone temple
#

Well I'd like to avoid that if at all possible, because it would require a gargantuan logistical effort to set that up.

violet vector
undone temple
#

Why can't that bloody OS just conform to normal unix system administration standards?! If I wanted a welded-shut box, I'd buy commercial and drop it on the sales rep's toes if it behaved as eratically as HA does at times!

#

Let's put a bookmark here, I need a good 8 hours of sleep to recharge my motivation and frustration tolerance.

violet vector
#

I think it's designed to be a "welded-shut box"

#

the debug option is available, so

#

don't forget to check the HA logs as well, in case anything obvious has been missed, such as go2rtc errors.

undone temple
#

If it's designed like a welded-shut box, it should work like one - flawlessly. If it constantly creates problems, denying people the opportunity to fix them without jumping through a million hoops will not make you a lot of friends.

#

I'm telling you, I'm THIS close to chucking the whole thing in the bin and buy something off the shelf...

#

Yes, I did check the HA logs, nothing related to go2rtc in there.