Having a problem with the hotspot setup on one of our routers.
The hotspot page that we’ve loaded onto the device is supposed to redirect users to a remote login page (I’ll use login.example.tld as an example)
login.example.tld has been added to the walled garden list but whenever I activate the hotspot and try to go somewhere I get a page saying:
ERROR: Not Found
Your cache administrator is webmaster.
Generated Sun, 23 Mar 2008 11:20:27 GMT by 10.60.4.1 (Mikrotik HttpProxy)
The system is setup with a dns name hotspots.example.tld which has been added into the static dns list, and the server profile also has this set as the dns name.
I’m stumped as a very similar configuration is working fine on a seperate device.
I am currently experiencing similar problems after moving from 2.9.50 to 3.6 - walled garden entries gives a proxy timeout even after disabling all web proxy / transparent proxy features.
Hey david, I ended up reseting the configuration on the devices and doing the following
Firstly, set the hotspot server address pool to none, then only specify a dns name for the hotspot server profile, don’t put in an IP address.
Then head to the user profiles and modify the default one so that transparent proxy is disabled.
Quite a process to fix it seems. I tested the walled garden on a stock router running a new install and it works fine - it seems the problem might be an upgrade issue from 2.9 to 3. I cant restore the production hotspot as easily, but I will let you know what happens when I get to it.
I’m having the same problem. I first did a netinstall of ROS 3.8, which was working ok. Then I upgraded to 3.9, and the proxy server
started itself up and now intercepts all of my redirect requests. Requests for URL’s in the walled garden work fine. Only redirects get the “Error: Not Found” from the proxy server.
I tried what you suggested, omega-00, but unfortunately the proxy server is still running and is still intercepting my redirects.
Under ip → web proxy → settings you can see the ‘running’ indicator in the lower left of the page. As soon as I start up the
hotspot server, the proxy server starts up. If I disable the hotspot server, the proxy server stops.
I have the hotspot default user profile set to not proxy and the other items you suggested, but that proxy server just keeps on running.
I sent a supout.rif to mikrotik. I hope they can get this fixed quickly or at least supply a work-around that works consistently.
If anyone else is seeing this problem, please post so we can get a sense of how widespread it is.
since version 3 mt has created a new proxy system which is still quite buggy (imho)
to stop the majority of traffic passing through this, head firstly to the default user profile for the hotspots and untick “use transparent proxy” this should now mean that the only pages passing through the proxy are the ones that redirect you to the login page initially.
Omega00 I tried all options for disabling the proxy. New information I have suggests that the custom website we use for the hotspot is based on version2.9 files, and there are now altered / additional files in version 3. We are updating the custom pages with a ver3 template to see if that solves the problem.
Thanks for the suggestions, but, as I said in my previous post,
I have the hotspot default user profile set to not proxy and the other items you suggested, but that proxy server just keeps on running.
However, I finally got the hotspot to work by re-booting the router. I had first tried stopping/starting the hotspot server, but
that still didn’t help. Only the reboot got it to stop the proxy server.
BTW, I wasn’t using the default user profile. I have a separate one that had “Transparent Proxy” unchecked from the beginning.
I guess just having the default profile with the proxy box checked, even though I wasn’t using that profile, broke the redirect.
Savagedavid, regarding the servlet files, we don’t use the MikroTik ones at all. We replace all of them with our own files which just redirect the user to our webserver. I’ll be interested to hear if you see any difference. Also, if you follow omega-00’s suggestions and then reboot, you may see the problem go away. That’s assuming, of course, you don’t want to use the proxy server at all.
I won’t say anything more. Just - I have the same problem and nothing solves this. F…cked shit.
I’m loosing money with theese v.3 experiments
I think, that the best method will be downgrade to 2.9.51 and do not touch it anymore.
It’s crazy!
kj
We have same problems with 40 hotspots and 1500+ users (RB333s/RB600s) its quite annoying cuz while we are rebooting our hotspots we must wait until some customers are logged in on every hotspot.
just got hit buy this today we use the hot spot on some cpes to define a proxy server under 2.9 it worked just fine now It kinda works on the rb411 but if you put it on a rb133 you will have to hyperterm it to disable the hotspot i am emailing a supout to mikrotik in hopes that it can be fixed ASAP for now i am down grading 133 boards to 2.9.51
I just got a reply from Sergejs at MikroTik, responding to my support request about this issue.
Transparent-proxy is enabled for all HotSpot users, which are using ‘ip
hotspot user profile’ default one.
HotSpot uses embedded proxy by default, set transparent-proxy=no to disable it
for HotSpot clients.
I responded that I had already unchecked the transparent proxy box, but I had to reboot and that the bug appears to be
the requirement to reboot the router to get the proxy to stop.
If I hear anything back, I’ll post it. Of course, if you are reading this, Sergejs, you can respond to this topic.
our sites have around 300 users each, and the hotspot system is setup to only use 2 pages directly off of the router
1 is the inital page they’re redirected to, which in turn redirects them to a remote page they login on
2 is the status window that pops up when they login
these are now the only 2 pages loading via the web-proxy and at peak times users report that the status page gives the connection reset message when refreshing.
looking now (12 at night at the site itself) there are 121 users currently logged in and web-proxy shows around 50 web-proxy connections, this rises higher during the day.
I encountered this problem with a test box (ROS 3.9) on my desk with no traffic and only one wireless client. My wireless client was able to reach any URL in the walled garden with no problem. If the wireless client tried to access a URL that was not in the walled garden, the client’s web browser displayed the built-in error message from the proxy server, “ERROR: Not Found”.
Un-checking the “transparent proxy” box did not eliminate the error. Stopping and starting the hotspot did not fix the error. Rebooting the node fixed the problem.
This problem does not appear to be load related at all. However, perhaps other users are having different problems with the proxy server enabled under load. I just wanted to turn it off and have it stay off.
dsobin, there are 2 seperate proxy issues that I have come across, the “Error Not found” and the “connection reset” messages.
As you have noted, the error not found occurs even with no load on the router, while the connection reset requires a number of connections to be made before the proxy stops responding to them
don’t know if this gives you any more ideas but i just received 2 support calls about users not being able to get up the Login page and instead receiving the “ERROR: Not Found” message. I then went over to have a look at the current proxy connections an noticed there are masses of connections showing up from the same IP’s.
If I clear these out they are all replaced within seconds. (Note no dst-address as they are connections trying to be made to the hotspot/status pages)
I have forwarded you a suppout.rif also.
Flags: S - server, C - client
# SRC-ADDRESS DST-ADDRESS PROTOCOL STATE TX-BYTES RX-BYTES
0 C 10.60.0.164 HTTP/1.0 rx-body 0 127
1 C 10.60.0.121 HTTP/1.0 rx-body 0 72
2 C 10.60.0.164 HTTP/1.0 rx-body 0 127
3 C 10.60.1.21 rx-header 0 83
4 C 10.60.0.121 HTTP/1.0 rx-body 0 72
5 C 10.60.0.121 rx-header 0 36
...
25 C 10.60.0.121 rx-header 0 38
26 C 10.60.0.164 HTTP/1.0 rx-body 0 127
27 C 10.60.0.19 HTTP/1.0 rx-body 0 56
28 C 10.60.0.164 HTTP/1.0 rx-body 0 127
29 C 10.60.0.121 rx-header 0 28
30 C 10.60.0.121 rx-header 0 37
...
72 C 10.60.0.19 rx-header 0 34
73 C 10.60.0.164 HTTP/1.0 rx-body 0 127
74 C 10.60.0.164 HTTP/1.0 rx-body 0 127
75 C 10.60.0.164 HTTP/1.0 rx-body 0 127
76 C 10.60.0.164 HTTP/1.0 rx-body 0 127
