web-proxy stops after upgrading to 6.46.6

RouterOS General
1

Guys, ive been scratching my head on this for a few hours now
Is anyone else having this problem after upgrading to latest stable, the web proxy stops after the first hit?

My router setup is as follows:
redirect port 80 traffic to internal proxy port eg 800 for transparency

First web request from internal client machine returns the url requested, afterwards, nothing.
Looking at the status of the web-proxy, its still running, but looking at web-proxy log, it says it stopped listening that the max memory or clients has been reached, even though my cache is neither near its limit nor is the value of max connections, and the next entry is the actual request that was returned to the client machine mentioned previously

This was def not a problem before I upgraded, and its not hardware specific in my case, seeing same issue on different model nr’s
I have played around with different combination of settings, but cant get it to not stop. Has anyone some sensible advice for my situation?

2

Same problem on 6.47 and 6.48.1.
The following message appears in log after the first request:

max client connection count or RAM limit reached: stop listening to port XXXX

There is enough free memory to process 242 bytes request.

[admin@xxx] > /system resource print
                  version: 6.48.1 (stable)
              free-memory: 5.9MiB
             total-memory: 32.0MiB
                 cpu-load: 9%
               board-name: RB SXT G-2HnD

Proxy configuration:

[admin@xxx] > /ip proxy print
                 enabled: yes
             src-address: ::
                    port: 9090
               anonymous: no
            parent-proxy: x.x.x.x
       parent-proxy-port: 81
     cache-administrator: webmaster
          max-cache-size: unlimited
   max-cache-object-size: 2048KiB
           cache-on-disk: no
  max-client-connections: 600
  max-server-connections: 600
          max-fresh-time: 10s
   serialize-connections: no
       always-from-cache: no
          cache-hit-dscp: 4
              cache-path: web-proxy1
3

Hello all,

Just for the record, I was experiencing this same error while running 6.45.8 on an RB941-2nD (hAP lite). It seems solved after upgrading to current stable (as of this writing) 6.48.3.

Never been able to find the root cause, however…

best,
cl.

4

Same here with RB751U running 6.48.6 and 6.49.6 :frowning: