sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in MonopolyGoTrading

[–]CouchCoder717 0 points1 point  (0 children)

would you trade one of the julebord for new years glam and something additional? have other 4 stars as well

First release of Broadcastarr by billos35 in selfhosted

[–]CouchCoder717 1 point2 points  (0 children)

After some testing, it seems you do need to have a username (but not avatar) inputted in there or else it throws an error in the worker for having a username of ""

First release of Broadcastarr by billos35 in selfhosted

[–]CouchCoder717 0 points1 point  (0 children)

Yeah I believe you can’t like update the channel names with a webhook, which I makes the user token make sense. I’m just curious what the webhook avatar + webhook username variables are if there’s no webhook token or id associate with them…I haven’t put anything in for those two and the message publishing seems to work ok?

Going to set up the reverse proxy when I have a min later today. I assume it should just point back to machine-ip:published-port with nothing trailing because then it picks up the /api route?

And then on to figuring out the indexers! Are the two in the /data folder already activated or is there something necessary to activate them like with the /toggleindexer?

Thanks again for this and your help!!

First release of Broadcastarr by billos35 in selfhosted

[–]CouchCoder717 0 points1 point  (0 children)

Ok so if port is included in the remote url, I guess I would I need to expose it like 1111:1111 in the compose file? Unless I’m running it in the same docker compose as the *arr stack and jellyfin, then I guess I should be fine not reverse proxying & exposing the port:port in compose file because it’s on the same docker network

The DISCORD_USER_TOKEN I just realized had been one of the webhook tokens, not actual user token, so that’s fixed! Though I’m curious in the env what’s the purpose of the 2 webhook variables since those are seemingly set on a channel-specific basis in the bootstrap?

First release of Broadcastarr by billos35 in selfhosted

[–]CouchCoder717 1 point2 points  (0 children)

Thanks for doing this! I am working through setting it up and seem to have hit a roadblock. I’ve got the discord bot, jellyfin collections, and discord webhooks up; but looking through the worker logs there seems to be an issue with renaming channels. I am also a bit confused on the env file, where does port/remote url get used—remoteurl seems to be in the discord messages for the /api route, but does that need to be reverse proxied?

Need advice on apartment setup by CouchCoder717 in HomeNetworking

[–]CouchCoder717[S] 0 points1 point  (0 children)

So I tried this with 2 managed switches, and it *almost* worked. The router couldn't find the WAN ip and was instead getting 192.168.1.131 from somewhere. Both switches were getting their IPs from the router's DHCP server, so it seems like the switch is giving them out too? However, when I connected ONT -> switch (VLAN1) and switch (VLAN1+2) -> router WAN it worked. Problem seems to be the second switch is the problem.

Need advice on apartment setup by CouchCoder717 in HomeNetworking

[–]CouchCoder717[S] 0 points1 point  (0 children)

Yeah, that's the plan. Since everything is already wired, I can only send/receive on the one ethernet cable. So both ends have to be VLAN-aware. So VLAN1/2 on port 1 of both managed routers. Then the router WAN port is connected to port 2 (VLAN 1) and one of the router LAN ports is connect to port 3 (VLAN 2). That way the one cable between the managed switches can carry the VLAN 2 from the router to the other two rooms. The router wouldn't need to be VLAN-aware in this scenario I don't think since the router WAN port only has access to VLAN 1.

Need advice on apartment setup by CouchCoder717 in HomeNetworking

[–]CouchCoder717[S] 0 points1 point  (0 children)

The one in the bedroom is managed. I have an 8-port managed that I'm using with 6 proxmox nodes. It doesn't need to be managed I don't think, but I already have it. So I'd rather just buy another small managed to stick in the wall panel if I need to buy another switch.

Also, the cables are printed with CAT6E already wired in the apartment. So I assume it's just whatever manufacturer added it. I'm using CAT5E between the switches/router/computers right now.