Skip to content

http traffic slow #255

Closed
Closed

Description

@TomBoehm

In "some locations" http traffic is terribly slow.
I face this on client side AND with one server side installation.
The server side installation, where I get this symptom uses a dual 5G and DSL connection
The values below are from a road warrior to a server that usually works fine:
While
iperf3 -s -p 8000 and

iperf3 -p 8000 -c 10.0.7.6
Connecting to host 10.0.7.6, port 8000
[  5] local 10.121.122.247 port 52265 connected to 10.0.7.6 port 8000
[ ID] Interval           Transfer     Bitrate
...               
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.01  sec  2.50 MBytes  2.10 Mbits/sec                  sender
[  5]   0.00-10.09  sec  2.50 MBytes  2.08 Mbits/sec                  receiver

is OK .... with same port, but http traffic:

python3 -m http.server
Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ...
172.18.0.2 - - [23/Apr/2026 10:25:17] "GET /testfile HTTP/1.1" 200 -

the result is:

curl http://10.0.7.6:8000/testfile > testfile
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  976k  100  976k    0     0  17071      0  0:00:58  0:00:58 --:--:-- 12942

And since we need http traffic to authenticate - that is slow too:

curl https://code.test.site/assets/index-iuvNiebc.js > index-iuvNiebc.js
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1108k  100 1108k    0     0  18930      0  0:00:59  0:00:59 --:--:-- 24366

The server side has no http traffic inspection.
My networking knowledge ends here ;-( maybe someone has an idea for me

Activity

  1. NHAS commented on Apr 23, 2026

    @NHAS
    Owner

    This is more of a support request than something being wrong with wag itself.

  2. Repository owner locked and limited conversation to collaborators on Apr 23, 2026
  3. converted this issue into a discussion #256 on Apr 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions