in this case, i used a vpn to connect elsewhere and changed the sever to the away link, however ive tried with 3 external machines with the same result.
I will look into it deeper.
1 Like
is there a port a need to forward that ive forgotten?
8089 seems to forward fine with the admin page..
I will have to modify Feral to work with session tokens and authentication headers. This will be on my list.
1 Like
I'm running 64-bit Windows 10 Pro. I'm installing the latest C++ redistributable now. It wants me to restart, which isn't convenient right now. I'll get 1.1.18 and see what happens. Do I need to restart before I can test properly?
1 Like
If you are busy, just wait until you have a convenient time to test, no rush. You can test before restart. I don't really know if the C++ update will help or not.
I installed & it wouldn't start. But I also added the latest c++ redistributable, which wants a restart before it kicks in. So when I have a chance to restart, I'll try again. Should I install again then, or just see if it runs? (That is, would install do anything different if the updated redistributables are present?)
Hold off on restarting. I think it is Windows 10 Pro that has this issue. The W10 Pro at work had the same issue. Let me dig deeper today and hopefully have a fix soon.
Ok, thanks. I'll be shutting down for the night in a few minutes anyway, so that will be a restart when I bring the box back up tomorrow.
I got it to work on my W10 Pro test machine. When you have time, download the 1.1.8 again and run it. I added some extra debugging on startup to it. You should see a file on your desktop named feral_crash_ui.txt. If it does not run correctly for you, paste the contents of that file. If the file does not generate, press Win + R, type %appdata%, and hit Enter.
- Open
FeralHTPCfolder - Inside that folder, create a new text file and name it
user_settings.json
add the following to that file:
{"EnableDebugLogging": true}
Save it and restart Feral.