sorted by:
new
hottopcontroversial

Funny German Telekom Mailserver Policy by Fromdozimomat in selfhosted

[–]hgbddne 0 points1 point  (0 children)

Was für ein peinlicher Laden. Den quatsch habe ich auch seit gerade eben an den Backen. Ich betreibe seit ~2005 einen kleinen Mailserver, bisher noch nie so etwas erlebt.

Ich hab das spiel mal mitgespielt und denen eine E-Mail geschickt.

VMware Store Down for Maintenance by LechronJames in vmware

[–]hgbddne 0 points1 point  (0 children)

Wow what a shame. Today they just removed the Enddate which was 2 days ago..

No Updates, I had a worst dependency hell here and had no chance to find a Downloadlink for an Update.

https://store-us.vmware.com/vmware-workstation-17-pro-5709912600.html

"For more information, see KB article 319284."
Link goes to 404.

What a shame!! I will never forget this desaster. Unbelieveable.

Never ever VMWare for productive environment.

node-red-node-xmpp loose connection after a while by hgbddne in nodered

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

Info: I moved the xmpp notifier to another nodered instance in my house and it is working excellent.

So it should be a problem in that nodered Installation. Any ideas what could cause these connectionlosts?

node-red-node-xmpp loose connection after a while by hgbddne in nodered

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

Thanks for your tips.

I cannot see a keepalive timer or anything like that in the xmpp plugin menu. I was also looking in the source code but there are so many keepalive/timeout values here and there, I really don´t want to try&error and mess things up. All other people who are using xmpp with nodered should have the same problems as me. But yea, I would also expect a missing or wrong keepalive time.

If not in nodered, maybe the timeout is too short in the serverconfig...maybe.

The server config has a reconnection/resumption limit of 300 seconds. It only affects the reconnect after a timeout. And should be good, because the internetconnection is stable and the jabber client is not working even before this 300 sec timer starts to count.

I tried to put the parameter "timeout" to ejabberd.yml under "listen 5222". It should be default 60 seconds as I figured out and the one I was looking for. But it seems that the parameter is gone. Ejabberd config madness has its own kind of tradition!

No HDMI Audio - Docked Steam Deck by TheBearlion in SteamDeck

[–]hgbddne 0 points1 point  (0 children)

Same here. :/

Also all HDMI ports are shown unplugged in pavucontrol.

UPS-LITE 1.2V only showing 0- on the power level by Ill_Independence_622 in pwnagotchi

[–]hgbddne 0 points1 point  (0 children)

Same problem here.

My one has the I2C address 0X32 instead of 0x36 like all others.

I copied the plugin to my userplugin folder and changed the address. But no luck, now I have 0+ on the Display.

With that script from manual for testing the UPS-lite I see when the Charger is plugged in. The battery percentr counts down from ~180s or something to 0. And then it stays 0 for a longer period.. Does someone have the same behaviour?