phoenixrisen

Having an issue where I cannot connect to the WebUI at all from any device. It was working a week or so ago the last time I logged in but not I cannot access it. Logs seem to show it starting and running correctly and I haven't changed any settings that would mess with this.

How do I find my docker network names when I can't start docker?

Initially had an issue with a drive failing to be recognized by the system. I ended up removing the drive and doing a new config since it was not being used anyways. However now docker service will not start at all. Have tried editing the vdisk size but made no difference. helmmemorycore-diagnostics-20250313-1923.zip

Having this issue where some images show up on actors etc but images in the journal don't show up, server gives 404 error. Checked the server directory and the files are present.

I've tried all of these.

Ive had this issue for about a year with different boards. Im close to giving up and trying to find cheap intel solution.

Without fail, the system becomes responsive after a few hours from boot. I have only seen this occur after switching to a ryzen CPU and board. I have tried two different boards and have the same issue. On each board I have change the power idle and c-state settings suggested in many other threads. Attached diagnostics and logs syslog-127.0.0.1.log helmmemorycore-diagnostics-20230917-1314.zip

Updated my bios, it seems to do better without hardlocking at disconnection but continues to drop from the network temporarily. syslog-127.0.0.1.log

Having an issue on server reset where all settings are reset to default, seemingly the entire .conf file is being overwritten like a new install every time I need to reboot the server. Ideas?

Recently upgraded my hardware with some spare pc components I had around. I switched from an older board with a i5 2500k to a newer asrock b450 board using a 3600x. I am aware of the issues that earlier Ryzen cpus had and disabled c states already in bios and in config/go but it still seems to crash every couple hours. This results in the server needing to be hard reset and performing a parity check each time. IS there something else I am missing or should I just go back to the old hardware? helmmemorycore-diagnostics-20221121-2152.zip

Tried it just now, I get the same output in the log.

I've been running a CoreKeeper server for a few weeks now, but the last night I restarted the container and now it doesnt appear to work. Log doesnt display the server ID to join:

Have been using this for a while now, but tonight it started to give this error and not load the page:

Beat me by seconds, I am having the same issue.