Following this issue, I decided to install Karaoke Mugen Portable on another user that I use for my smb client. After setting up the app according to this with the FTP login provided years ago, i am presented with the attached images and logs. Anything I can do from here? Regenerating database fails as no media is found.
For context, in this new local account profile, Cloudflare WARP is not installed or enabled.
one more thing to mention is i have also switched internet providers from More Telecom to DODO internet, so hopefully this makes things easier
Apparently the host key scan for the repository isn’t happening even though it should. This is weird and we’ll look into it.
What’s the contents of the app/SSHKeys folder in your KM app folder ? I want to know if there’s a known_hosts_KaraokeMugen_kara.moe file and what its contents are.
Pinging @RoyceThomas since I’m not sure if you’re notified of new messages because I just split this topic
Hi Axel
Sorry for the late reply, and for replying to the previous issue I had.
The folder you have requested has these three files.
As always thanks for your help.
You need to use the next version since you’re a maintainer as we sometimes push changes to that branch that only affect maintainers.
In the meantime can you try removing the known_hosts file (and only that one) and trying again?
The “next” versions is currently “extracting database”. I’ll let this finish before switching over the db to maintainer mode and fill up my login info. I removed the master version from the desktop to keep things partitioned. My latency is around 300ms and sometimes dips into the 310-1500 range and I get a warning… Well that is probably to be expected way down under in Australia…
Anyway Ill keep you posted if I’m able to push a song, and edit a song successfully, but as it looks now, i think the issue may be solved…
Edit:… umm i dont think i can test to remove the known_hosts file method as i deleted the master portable before you sent this, i’m sorry 
It’s okay, we identified the issue and we’ll try to find a way so it doesn’t happen again. Deleting the file would have fixed your initial problem though 
I’ll consider this solved.
