Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    speedtest CLI dying out

    Scheduled Pinned Locked Moved pfSense Packages
    28 Posts 8 Posters 9.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gnitingG
      gniting @gniting
      last edited by gniting

      Indeed it is an upstream issue.

      1 Reply Last reply Reply Quote 0
      • fireodoF
        fireodo @gniting
        last edited by

        @ibbetsion

        Same error here too! I opened another thread earlyer this morning ...
        Speedtest

        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
        pfsense 2.8.0 CE
        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

        gnitingG 1 Reply Last reply Reply Quote 0
        • gnitingG
          gniting @fireodo
          last edited by

          @fireodo said in speedtest CLI dying out:

          @ibbetsion

          Same error here too! I opened another thread earlyer this morning ...
          Speedtest

          Here's the temp fix:

          1. open up /usr/local/lib/python3.7/site-packages/speedtest.py
          2. go to line 1174
          3. comment out the line map(int, server_config['ignoreids'].split(',')) using a #
          4. add this line
          map(int, (server_config['ignoreids'].split(',') if len(server_config['ignoreids']) else []) )
          
          1. save and you're done.. it'll work "normally" now

          your changes will be overwritten once the package updates, which is ok cause the upstream patch is to change that exact line the same way.

          fireodoF 1 Reply Last reply Reply Quote 4
          • provelsP
            provels
            last edited by provels

            The Windows server I have running the CL on Python 2.7 shows same error. Them not us. But the Win util is working fine.

            Broke at 1630 Chicago time yesterday.

            Peder

            MAIN - pfSense+ 24.11-RELEASE - Adlink MXE-5401, i7, 16 GB RAM, 64 GB SSD. 500 GB HDD for SyslogNG
            BACKUP - pfSense+ 23.01-RELEASE - Hyper-V Virtual Machine, Gen 1, 2 v-CPUs, 3 GB RAM, 8GB VHDX (Dynamic)

            1 Reply Last reply Reply Quote 0
            • fireodoF
              fireodo @gniting
              last edited by

              @ibbetsion said in speedtest CLI dying out:

              @fireodo said in speedtest CLI dying out:

              @ibbetsion

              Same error here too! I opened another thread earlyer this morning ...
              Speedtest

              Here's the temp fix:

              1. open up /usr/local/lib/python3.7/site-packages/speedtest.py
              2. go to line 1174
              3. comment out the line map(int, server_config['ignoreids'].split(',')) using a #
              4. add this line
              map(int, (server_config['ignoreids'].split(',') if len(server_config['ignoreids']) else []) )
              
              1. save and you're done.. it'll work "normally" now

              Done, and confirm its working. Thank you!

              Regards,
              fireodo

              Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
              SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
              pfsense 2.8.0 CE
              Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

              1 Reply Last reply Reply Quote 3
              • K
                KevinRice
                last edited by

                Speedtest 2.1.3 Released

                Speedtest 2.1.2 broke yesterday and stopped working, producing the error message:

                ValueError: invalid literal for int() with base 10: ''.

                Version 2.1.3 has been posted by the author, but has not yet been picked up into the package repositories.

                Since a package update doesn't work, this manual update method worked for me in the interim:

                # CONFIRM VERSION
                : speedtest --version
                speedtest-cli 2.1.2
                Python 3.7.9 (default, Feb  5 2021, 20:17:58) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a
                
                # CHANGE TO PYTHON PACKAGE DIRECTORY
                : cd /usr/local/lib/python3.7/site-packages
                
                # MANUALLY DOWNLOAD NEWEST .PY FILE
                : curl -Lo speedtest.py https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py
                
                # CONFIRM VERSION
                : speedtest --version
                speedtest-cli 2.1.3
                Python 3.7.9 (default, Feb  5 2021, 20:17:58) [Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a
                
                
                S 1 Reply Last reply Reply Quote 6
                • S
                  sschueller @KevinRice
                  last edited by

                  In case anyone is still having issues with the python version (and is running x86 hw). Speedtest net (speedtest dot net/apps/cli) has released their own version which is written in C and also supports settings which interface you want to use for the test.

                  gnitingG 1 Reply Last reply Reply Quote 0
                  • gnitingG
                    gniting @sschueller
                    last edited by

                    @sschueller they have a pfsense specific package? if not, then won't it get wiped with every upgrade?

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      sschueller @gniting
                      last edited by

                      @ibbetsion not at the moment (on reddit there was an exchange between netgate and speedtest so their may be one in the future), you need to install it via cli and it will be gone after update. However during my last update the python version was also gone.

                      E 1 Reply Last reply Reply Quote 0
                      • E
                        egeekial @sschueller
                        last edited by

                        The new Ookla FreeBSD version works fine.

                        # REMOVE OLD VERSION
                        : pkg remove py37-speedtest-cli
                        
                        # INSTALL NEW OOKLA VERSION
                        : pkg add "https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-freebsd.pkg"
                        
                        fireodoF 1 Reply Last reply Reply Quote 0
                        • S
                          SpecimenB
                          last edited by

                          @egeekial said in speedtest CLI dying out:

                          pkg add "https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-freebsd.pkg"

                          Certificate verification failed for /C=BE/O=GlobalSign nv-sa/CN=GlobalSign Atlas R3 DV TLS CA 2020
                          1078788096:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2102_2-aarch64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
                          Certificate verification failed for /C=BE/O=GlobalSign nv-sa/CN=GlobalSign Atlas R3 DV TLS CA 2020
                          1078788096:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2102_2-aarch64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
                          Certificate verification failed for /C=BE/O=GlobalSign nv-sa/CN=GlobalSign Atlas R3 DV TLS CA 2020
                          1078788096:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/build/plus-crossbuild-2102_2-aarch64/sources/FreeBSD-src/crypto/openssl/ssl/statem/statem_clnt.c:1915:
                          pkg: https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-freebsd.pkg: Authentication error

                          1 Reply Last reply Reply Quote 0
                          • fireodoF
                            fireodo @egeekial
                            last edited by fireodo

                            @egeekial said in speedtest CLI dying out:

                            The new Ookla FreeBSD version works fine.

                            Hi,
                            Is this Version also working with the Speedtest Widget?
                            Thanks
                            fireodo

                            Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                            SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                            pfsense 2.8.0 CE
                            Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                            1 Reply Last reply Reply Quote 1
                            • SebMS
                              SebM
                              last edited by

                              This method is pretty bulletproof for me:

                              As per this page How To Install Speedtest-cli On a FreeBSD To Check Internet Speed, I simply ran these two commands in the GUI at Diagnostics / Command Prompt / Execute Shell Command:

                              pkg search speedtest
                              

                              This returned the following:
                              py38-speedtest-cli-2.1.3
                              Command line interface for testing internet bandwidth

                              so I ran this command:

                              pkg install -y py38-speedtest-cli-2.1.3
                              

                              Then from there I simply run speedtest

                              K 1 Reply Last reply Reply Quote 0
                              • K
                                KevinRice @SebM
                                last edited by

                                @sebm That method works because the issue has been fixed. Previously, it was broken.

                                SebMS 1 Reply Last reply Reply Quote 0
                                • SebMS
                                  SebM @KevinRice
                                  last edited by

                                  @kevinrice Great, so now that it's been fixed and I wrote down a simple step-by-step, anybody who comes here in the future knows what to do... I love it when a plan comes together!

                                  K 1 Reply Last reply Reply Quote 0
                                  • K
                                    KevinRice @SebM
                                    last edited by

                                    @sebm Until it breaks next revision! ;)

                                    SebMS 1 Reply Last reply Reply Quote 0
                                    • SebMS
                                      SebM @KevinRice
                                      last edited by

                                      @kevinrice Then one can browse to Ookla's Speedtest, run:

                                      sudo pkg add "https://install.speedtest.net/app/cli/ookla-speedtest-1.0.0-freebsd.pkg"
                                      

                                      Then when this is fixed, they can run:

                                      pkg remove --y speedtest
                                      

                                      And rinse and repeat steps from there:
                                      @sebm said in speedtest CLI dying out:

                                      Simple. Unintrusive. I likes 😊

                                      K 1 Reply Last reply Reply Quote 0
                                      • K
                                        KevinRice @SebM
                                        last edited by

                                        @sebm Until Ookla revises... Never ending battle.

                                        SebMS 1 Reply Last reply Reply Quote 0
                                        • SebMS
                                          SebM @KevinRice
                                          last edited by

                                          @kevinrice I'd like to thank you for having published a workaround (option #3).

                                          K 2 Replies Last reply Reply Quote 0
                                          • K
                                            KevinRice @SebM
                                            last edited by

                                            @sebm And, thank you for providing the current solution! I'm actually going to use it right now.

                                            1 Reply Last reply Reply Quote 1
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.