It keeps telling me i'm logged out when I log in. but by accesssing mudfish.net i can log in easily.
Tried changing the settings between Full VPN mode and normal but no differences.

Normally it means Mudfish Launcher failed to access master server. Did you try with Firewall Issues link?

Yes. I tried both the -o and the -t option. It gives the exact same thing as the picture.
I feel that it's my account being bugged or something maybe?

Ok It works at my home wifi but not at my school wifi. I know it's because my school wifi has firewall. Is it because I have to run mudfish once at home before I can use it to bypass firewalls?

Nope. Still doesn't work in school. Wasn't Mufish able to bypass Firewalls?

Did you try with -t option alone? I'm not sure how your school detects the mudfish connection, but I need to see more details what's happening on your network environment. Could you please send me a problem report if possible? (see Sending the Problem Report link.)

Yes I tried with -t alone and -o alone, restarting the application.
I can't find the problem report link http://imgur.com/c6lAiSI .
The school doesn't block free VPNs so I'm not sure how are they blocking Mudfish.

The problem report link is only shown when you're accessing the dashboard with Mudfish Launcher not just visiting mudfish.net site. If the school network allows free VPNs no reason mudfish isn't working. Hmm.. I can see more details when I get a problem report.

Mudfish launcher also doesnt have that icon

Still weird. Could you try to access directly to http://127.0.0.1:8282/admin/prog/report_problem link?

Yep I can. Just sent the problem report.

I'm not sure that it's blocked too because on my side I couldn't see any reports from your side. :-( Could you please check Sending the Problem Report link again to see about how to send the problem report manually? Sorry for delays to solve your problem.

ok done it a few days ago.
[Mudfish Networks #98633]

Ooops. It seems I'd missed your report. Now I'd checked and have some questions.

* When I looked into your problem report, it seems you ran 'muddiag.exe -o' command while the mudfish isn't running. The command makes a better problem report when the mudfish is running.
* It seems your network administrator blocks at least TCP port 10007 and 10008 ports. However I'm not sure that they blocked the authentication server also. At http://mudfish.net/releases/ link, you can find a v4.3.10 version built for your cases. Could you please install it and then send a problem report again for me? At there, it has more verbose log messages.

Ok. I did as you said and sent another ticket at [Mudfish Networks #98792]

Yes.. I'd checked and found that your network administrator installed web firewall and it looks all web traffics (to port 80) are monitored and filtered by web firewall. A good news is I found that the firewall doesn't filter SSL (port 443) traffics so we can try another patches. I'll let you know when the patch is available.

However according to your problem report, it seems sometimes mudfish was fine to run because I can see the following logs.

[0.003999] [INFO] mudfish v4.3.10 (for x86_64)
[0.003999] [INFO] Timestamp: Mon Nov 09 08:07:04 2015

[0.003999] [INFO] Connection protocol: tcp_https
[0.003999] [INFO] Authenticating...
[0.386287] [INFO] Fetching the static node for v2...
[1.134831] [INFO] TAP-Win32 Driver GUID {9DE81755-DD09-471C-98FE-445E82AB9C4C}

These lines mean that at Mon Nov 09 08:07:04 2015, mudfish launched successfully on your environment. At that moment, were you on other location?

I was using my laptop at school at that time with school wifi I think but I don't remember running Mudfish. All I did was just run Discord and play Modern Warfare 3 in Steam Offline mode. I'm pretty sure if Steam was in offline mode, it most probably meant that I never turned on any VPN as Steam is blocked by my school.
EDIT: Yes I did run Mudfish at that time to do the problem report thing.

I see. At http://mudfish.net/releases/ link, you can find v4.3.10 (yes same with last but it's refreshed version) package for you. Please remove the previous mudfish and re-install this new package then try. At this moment please follow the below steps:

* After reinstalling mudfish v4.3.10. Removes -t or -O options used by Mudfish icon's property. At this package, port 443 is used for authentication as default. If it's not still helpful, you can try with -t option.
* For connection protocol, you should use only 'TCP Port 443' or 'UDP Port 53 (not sure)'. It seems other options aren't working for your environment.

Ok I managed to log in from the Mudfish launcher and it shows self-set up at 100%. But now there's a new error (image below). When I click "Yes" it brings me to a korean help page and google translate doesn't handle it so well. Tried all the options above.
http://i.imgur.com/xFPDbJU.png

Oh oh.... Did you enable Full VPN mode at that moment? Could you please test it again after disabling Full VPN mode? It seems this issue could happen if it's on.... If it works afer disabling it, it looks I made a wrong package with missing one line code. :-(

Hmm there seems to be no errors with Full VPN off. But I have no way to test if it works properly since my games requires steam to start (and I can only find the item for Steam site, not the steam app).

I think you can follow Quickstart for v4 link to test the basic functionalities. If it works, you can assume that everything is working correctly except Full VPN.

Yep it seems to work for steam and Tree of Savior but it keeps giving DNS problems often in browser.

OK I got it. I'll release new one for you to enable the Full VPN mode. However I think DNS problem could be different because at that moment I didn't use Full VPN mode when mudfish turned on. It means DNS requests are all passed using your default gateway or path. Not to mudfish (so DNS requests aren't handled by mudfish at least). Is it only happen when mudfish is running?

Yes. it happens when mudfish is running. When i turned it off the browser instantly works normally.

Very weird. Unless you're using Full VPN mode, your DNS requests wouldn't be redirected to Mudfish nodes. Could you please check http://windows.microsoft.com/en-us/windows/change-network-protocol-bindings-order#1TC=windows-7 link? Ans try with changing the ordering of your network interfaces.

Ok everything seems to be working fine. DNS failure was probably some weird random internet error at that time. It seems to be working properly now. Thanks for your help.

Good to know. :-) Today I'd released v4.3.11 which addresses your Full VPN mode issue. If you have a chance, please test with it whether it's working for your environment too.