[Support] binhex - qBittorrentVPN

[postinox]

hi everyone, I have some issues related with upload speed and after read FAQ and many threads and posts about different issues with down/up speeds I did all these steps: reinstall docker image, delete config folder, check the forward port with the VPN provider (mullvad/wireguard server), check my folder structure and permissions (TRaSH Guide), check my firewall policies, even change my cache drives for separate the pools for appdata and other for downloads and the results are the same. I have 1Gb of symmetrical home fiber connection but my upload speeds goes to KiB/s and even Bs rarely I did see one torrent goes over 1 or 2 Mb/s:

qbittorent config:

Spoiler

 

I found this thread https://github.com/qbittorrent/qBittorrent/issues/14844 and thinking that maybe my issue can be related with IO reads. here is my log file if can help me try to figure out how to solve this. tell me if need any other details.

thanks!

 

 

supervisord.log

[NotABanana]

I had this issue previously with deluge and now I've migrated to qbittorrent and having the same issue. I am using mullvad vpn via wireguard with a wg0.conf file. It is successfully connecting to the VPN but the webui is unavailable. With the VPN disabled webui works fine.

supervisor.log

[binhex]

15 hours ago, postinox said:

but my upload speeds goes to KiB/s and even Bs rarely I did see one torrent goes over 1 or 2 Mb/s:

i see you are with a custom vpn provider, have you assigned an port forward  from your vpn provider and have you configured qbittorrent to use it?, my guess would be no thus leading to poor uploads.

[binhex]

8 hours ago, NotABanana said:

I had this issue previously with deluge and now I've migrated to qbittorrent and having the same issue. I am using mullvad vpn via wireguard with a wg0.conf file. It is successfully connecting to the VPN but the webui is unavailable. With the VPN disabled webui works fine.

supervisor.log 21.8 kB · 0 downloads

thats a successful start, two questions:-

1. what is the ip of the machine running the web browser that you are using to attempt connection to the qbittorrent web ui?

2. what is the 'network Type' set to for the container?, the default is bridge.

[postinox]

1 hour ago, binhex said:

i see you are with a custom vpn provider, have you assigned an port forward  from your vpn provider and have you configured qbittorrent to use it?, my guess would be no thus leading to poor uploads.

Hi binhex first of all thanks for all your help and contributions I do a lot of stuff thank to your dockers .

I configured the forward port in qbittorrent according to the port that I did create in mullvad page (tested in firefox docker):

Spoiler

 

 

 

Speedtest:

Also now my concern is that in mullvad tool for connection check show me the "Leaking WebRTC IPs" in red and this show me the real IP and don't know if this is total normal or maybe is related with some issue in the configuration or connection of the VPN.

Spoiler

more details about my config in unraid:

Spoiler

Nvme cache disk for appdata and SSD cache disk for downloads

 

 

 

Qbittorrent advanced:

 

With this config in my qbit now I try to seed around 330 torrents files (all of them from private trackers).

Attached my ifconfig output if this show some issue.

do you recommend use PIA template and try to connect to the wireguard tunnel with this?

once again thanks for your support!

 

ifconfig.txt

[NotABanana]

4 hours ago, binhex said:

thats a successful start, two questions:-

1. what is the ip of the machine running the web browser that you are using to attempt connection to the qbittorrent web ui?

2. what is the 'network Type' set to for the container?, the default is bridge.

1. 192.168.4.26

 

2. Bridge, the default.

 

 

I see what I've done wrong now, thanks! For anyone else reading this if your router uses anything other than 192.168.1.x, make sure you set "lan network" correctly. 

Edited March 3, 2023 by NotABanana
I stopped being dumb

[Jparslow96]

Just wanted to jump on the wagon with Postinox's point. I just signed up for Mullvad and can't get any speeds past 1.2MB/s. Originally tried Wireguard - and just now tried OpenVPN and it's the same deal. Port forwarded as well. Settings match Postinox.

Start log.txt

[binhex]

12 hours ago, Jparslow96 said:

Just wanted to jump on the wagon with Postinox's point. I just signed up for Mullvad and can't get any speeds past 1.2MB/s. Originally tried Wireguard - and just now tried OpenVPN and it's the same deal. Port forwarded as well. Settings match Postinox.

Start log.txt 5.62 kB · 0 downloads

check Q3:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

[Jparslow96]

1 hour ago, binhex said:

check Q3:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Thanks Binhex!

I actually did try this previously and it didn't seem to make a difference. But now it does. I guess stopping and restarting the docker is needed to apply this change. 

Full speeds now - and confirmed IP is linked to the VPN. Thanks for your help and great work!

[sillstrybarn]

I'm courious if anyone else got the same problem with this docker.
I've been using it for a couple of years now and it happens from time to time.

The docker seems to crash and the unraid webui becomes unresponsive.
I've tried a couple of different methods to kill the docker, but it always  ends with rebooting the server.

I've been using it with Nordvpn before and now Im using mullvad vpn. Earlier I did not use privoxy, but now my prowlarr docker is connecting via the privoxy.
Cannot see anything obvious in the logs what is causing the "crash".

 

When this happened like two hours ago, I tried stopping docker service via ssh. It says something like "cannot stop docker qbit".

But the service stops. And the webui gets responsive again. But then i cannot start the docker service bacause "docker.img is in use".

So i tried to stop the array. But then the log said it "cannot unmount /mnt/cache because its busy".
So I tried a command I read in another thread on the forums "lsof /mnt/cache". And it listed a few .lock-files in the qbit-appdata folder.
My appdata is stored on the cache only.

Then i tried reboot, but I guess that was not a clean one, because it started a parity sync on startup.

Where to look for a solution?

 

Is this what's causing me problem? 

 

Edited March 6, 2023 by sillstrybarn

[jcarre]

23 hours ago, sillstrybarn said:

I'm courious if anyone else got the same problem with this docker.
I've been using it for a couple of years now and it happens from time to time.

The docker seems to crash and the unraid webui becomes unresponsive.
I've tried a couple of different methods to kill the docker, but it always  ends with rebooting the server.

 

I am having exactly the same problem. Qbitorrent crashes with a:

 

Quote

Jan 11 10:07:16 ivpiter kernel: BUG: kernel NULL pointer dereference, address: 0000000000000076
Jan 11 10:07:16 ivpiter kernel: #PF: supervisor read access in kernel mode
Jan 11 10:07:16 ivpiter kernel: #PF: error_code(0x0000) - not-present page
Jan 11 10:07:16 ivpiter kernel: PGD 0 P4D 0 
Jan 11 10:07:16 ivpiter kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Jan 11 10:07:16 ivpiter kernel: CPU: 6 PID: 15256 Comm: qbittorrent-nox Tainted: G           O      5.19.17-Unraid #2
Jan 11 10:07:16 ivpiter kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS MASTER/X570 AORUS MASTER, BIOS F36f 07/20/2022
Jan 11 10:07:16 ivpiter kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
Jan 11 10:07:16 ivpiter kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b e9 ef 59 a6 00 <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
Jan 11 10:07:16 ivpiter kernel: RSP: 0000:ffffc90015a17cc0 EFLAGS: 00010246
Jan 11 10:07:16 ivpiter kernel: RAX: 0000000000000042 RBX: 0000000000000042 RCX: 0000000000000042
Jan 11 10:07:16 ivpiter kernel: RDX: 0000000000000001 RSI: ffff888ed6b1c6d8 RDI: 0000000000000042
Jan 11 10:07:16 ivpiter kernel: RBP: 0000000000000000 R08: 0000000000000014 R09: ffffc90015a17cd0
Jan 11 10:07:16 ivpiter kernel: R10: ffffc90015a17cd0 R11: ffffc90015a17d48 R12: 0000000000000000
Jan 11 10:07:16 ivpiter kernel: R13: ffff888e61e37e38 R14: 0000000000053017 R15: ffff888e61e37e40
Jan 11 10:07:16 ivpiter kernel: FS:  000014794e5436c0(0000) GS:ffff888ffe980000(0000) knlGS:0000000000000000
Jan 11 10:07:16 ivpiter kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 11 10:07:16 ivpiter kernel: CR2: 0000000000000076 CR3: 0000000d4caa4000 CR4: 0000000000350ee0
Jan 11 10:07:16 ivpiter kernel: Call Trace:
Jan 11 10:07:16 ivpiter kernel: <TASK>
Jan 11 10:07:16 ivpiter kernel: __filemap_get_folio+0x98/0x1ff
Jan 11 10:07:16 ivpiter kernel: ? _raw_spin_unlock+0x14/0x29
Jan 11 10:07:16 ivpiter kernel: filemap_fault+0x6e/0x524
Jan 11 10:07:16 ivpiter kernel: __do_fault+0x30/0x6e
Jan 11 10:07:16 ivpiter kernel: __handle_mm_fault+0x9a5/0xc7d
Jan 11 10:07:16 ivpiter kernel: handle_mm_fault+0x113/0x1d7
Jan 11 10:07:16 ivpiter kernel: do_user_addr_fault+0x36a/0x514
Jan 11 10:07:16 ivpiter kernel: exc_page_fault+0xfc/0x11e
Jan 11 10:07:16 ivpiter kernel: asm_exc_page_fault+0x22/0x30
Jan 11 10:07:16 ivpiter kernel: RIP: 0033:0x147facac47c1
Jan 11 10:07:16 ivpiter kernel: Code: 48 01 d0 eb 1b 0f 1f 40 00 f3 0f 1e fa 48 39 d1 0f 82 53 2b fc ff 0f 1f 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 0f 82 af 00 00 00 <c5> fe 6f 06 48 83 fa 40 0f 87 3e 01 00 00 c5 fe 6f 4c 16 e0 c5 fe
Jan 11 10:07:16 ivpiter kernel: RSP: 002b:000014794e5412c8 EFLAGS: 00010202
Jan 11 10:07:16 ivpiter kernel: RAX: 00001404bc0008e0 RBX: 000014794e542308 RCX: 000014794e541500
Jan 11 10:07:16 ivpiter kernel: RDX: 0000000000004000 RSI: 0000146e25217fe1 RDI: 00001404bc0008e0
Jan 11 10:07:16 ivpiter kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Jan 11 10:07:16 ivpiter kernel: R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
Jan 11 10:07:16 ivpiter kernel: R13: 00001404bc04ac10 R14: 0000000000000001 R15: 0000147fa46d1ae0
Jan 11 10:07:16 ivpiter kernel: </TASK>
Jan 11 10:07:16 ivpiter kernel: Modules linked in: tcp_diag udp_diag inet_diag veth xt_nat ipvlan nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_nat nf_nat vhost_net tun vhost vhost_iotlb tap xfs md_mod efivarfs xt_connmark nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_mark iptable_mangle xt_comment xt_addrtype iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls mlx4_en mlx4_core igb i2c_algo_bit r8169 realtek mpt3sas btusb it87(O) btrtl btbcm edac_mce_amd gigabyte_wmi wmi_bmof mxm_wmi edac_core kvm_amd hwmon_vid kvm crct10dif_pclmul btintel crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd bluetooth raid_class ahci nvme ecdh_generic rapl k10temp ccp i2c_piix4
Jan 11 10:07:16 ivpiter kernel: scsi_transport_sas libahci ecc tpm_crb i2c_core nvme_core tpm_tis thermal tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: mlx4_core]
Jan 11 10:07:16 ivpiter kernel: CR2: 0000000000000076
Jan 11 10:07:16 ivpiter kernel: ---[ end trace 0000000000000000 ]---
Jan 11 10:07:16 ivpiter kernel: RIP: 0010:folio_try_get_rcu+0x0/0x21
Jan 11 10:07:16 ivpiter kernel: Code: e8 9d fd 67 00 48 8b 84 24 80 00 00 00 65 48 2b 04 25 28 00 00 00 74 05 e8 c1 35 69 00 48 81 c4 88 00 00 00 5b e9 ef 59 a6 00 <8b> 57 34 85 d2 74 10 8d 4a 01 89 d0 f0 0f b1 4f 34 74 04 89 c2 eb
Jan 11 10:07:16 ivpiter kernel: RSP: 0000:ffffc90015a17cc0 EFLAGS: 00010246
Jan 11 10:07:16 ivpiter kernel: RAX: 0000000000000042 RBX: 0000000000000042 RCX: 0000000000000042
Jan 11 10:07:16 ivpiter kernel: RDX: 0000000000000001 RSI: ffff888ed6b1c6d8 RDI: 0000000000000042
Jan 11 10:07:16 ivpiter kernel: RBP: 0000000000000000 R08: 0000000000000014 R09: ffffc90015a17cd0
Jan 11 10:07:16 ivpiter kernel: R10: ffffc90015a17cd0 R11: ffffc90015a17d48 R12: 0000000000000000
Jan 11 10:07:16 ivpiter kernel: R13: ffff888e61e37e38 R14: 0000000000053017 R15: ffff888e61e37e40
Jan 11 10:07:16 ivpiter kernel: FS:  000014794e5436c0(0000) GS:ffff888ffe980000(0000) knlGS:0000000000000000
Jan 11 10:07:16 ivpiter kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 11 10:07:16 ivpiter kernel: CR2: 0000000000000076 CR3: 0000000d4caa4000 CR4: 0000000000350ee0

 

 

When this happens web ui becomes unresponsive, docker kill makes the ui work again, but qbitorrent won't restart correctly. 
The only fix is to restart docker, which will not start again for me until I fully restart.
I also have the umount error while turning off the array.

 

The problem seemed to go away after last update, I got a couple days uptime. But it happened twice yesterday.

[sillstrybarn]

2 hours ago, jcarre said:

 

I am having exactly the same problem. Qbitorrent crashes with a:

 

 

 

When this happens web ui becomes unresponsive, docker kill makes the ui work again, but qbitorrent won't restart correctly. 
The only fix is to restart docker, which will not start again for me until I fully restart.
I also have the umount error while turning off the array.

 

The problem seemed to go away after last update, I got a couple days uptime. But it happened twice yesterday.

I've rolled back qbit to 4.3.9 now. Hope that helps. 

[doubleopinter]

On 3/4/2023 at 1:10 PM, Jparslow96 said:

Thanks Binhex!

I actually did try this previously and it didn't seem to make a difference. But now it does. I guess stopping and restarting the docker is needed to apply this change. 

Full speeds now - and confirmed IP is linked to the VPN. Thanks for your help and great work!

 

Hey I just came here to discuss the same thing, I don't think it's TCP vs uTP cause I changed it to TCP only right away. I am on Mullvad as well. Using Wireguard. I'm running all of this in docker myself. I have the same host with both rTorretnVPN and qBitTorrentVPN. I have wireguard configs to the same place for both of them. rTorrentVPN maxes out my full 100Mbit connection. qBit maxes out at 10 and then fluctuates.

 

I also have qbit at home and it's been really slow vs when I ran rtorrentvpn, which would almost max out my 1gb connection.

 

I'm going to set qbit up on unraid and try it that way to rule out weirdness.

Edited March 8, 2023 by doubleopinter

[DoeBoye]

On 3/7/2023 at 1:05 PM, jcarre said:

 

I am having exactly the same problem. Qbitorrent crashes with a:

 

 

 

When this happens web ui becomes unresponsive, docker kill makes the ui work again, but qbitorrent won't restart correctly. 
The only fix is to restart docker, which will not start again for me until I fully restart.
I also have the umount error while turning off the array.

 

The problem seemed to go away after last update, I got a couple days uptime. But it happened twice yesterday.

I'm having the same problem. I always notice when I can no longer load the unRaid webgui. All my other dockers but qbittorrent are running and accessible. I can ssh into the server without issue. When I try and stop docker, I get the error that it could not stop qbitorrent. Same for stopping nginx (unless I try and stop docker first). I usually end up rebooting.

[momoz]

Having an issue the last few weeks with vPN..  I use NordVPN (Wireguard configs) and it seems the tunnel stops working (UI works, but no data flow, unable to ping when in console).

 

stopping/restarting container seems to fix the issue.. sometimes I've noticed the container doesn't connect to VPN which then causes the UI to never load (never gets to "listening on port.. "

 

Anyone see this issue?

[ezzys]

I have just installed qbitorrentvpn, however I cannot seem to get the WEBUI to work. I am using PIA VPN.

 

The logs suggest it is all working. The final message in the log afer a restart is:

2023-03-11 17:08:47,265 DEBG 'watchdog-script' stdout output:
[info] qBittorrent process listening on port 8082

 

I did change the ports as I had a clash, but made sure I was consistant with what I changed.

 

Host Port 1 Containter Port: 6881 = 6881

Host Port 2 Containter Port: 6881 = 6881

Host Port 3 Container Port: 8080 = 8082

Host Port 4 Container Port: 8118 = 8128

Container Variable: WEBUI+PORT = 8082

 

After leaving it run for a while I just see the following in the log

2023-03-12 19:38:49,166 DEBG 'start-script' stdout output:
[info] Successfully assigned and bound incoming port '54605'

 

Any suggestions on what to adjust, any log information that will help troubleshoot?

 

 

Edited March 12, 2023 by ezzys
added log output

[gustyScanner]

Has anyone had an issue with the qBittorrent webui not loading when using Wireguard? I can use OpenVPN and the webui then loads fine.

 

If I read the logs on both Wireguard and OpenVPN I can see it made connections to the proper VPN (and if I use a command within the container, they do have network connection curl icanhazip.com)

 

I wonder what it is about using Wireguard that breaks the qBittorrent UI for me.

[Johnster]

Since rTorrent is discontinued, i am looking forward to installing qBittorrent. Does anyone know how to migrate from rTorrent to qBittorrent while retaining stats? Thank you!

[milman21]

On 3/13/2023 at 6:44 AM, ezzys said:

I did change the ports as I had a clash, but made sure I was consistant with what I changed.

 

Host Port 1 Containter Port: 6881 = 6881

Host Port 2 Containter Port: 6881 = 6881

Host Port 3 Container Port: 8080 = 8082

Host Port 4 Container Port: 8118 = 8128

Container Variable: WEBUI+PORT = 8082

 

Any suggestions on what to adjust, any log information that will help troubleshoot?

 

 

According to the FAQ, you may need to remove "Host Port 3 Container Port", and manually add WEBUI_PORT (not WEBUI+PORT) as 8082. See here

[ezzys]

On 3/16/2023 at 2:20 PM, milman21 said:

According to the FAQ, you may need to remove "Host Port 3 Container Port", and manually add WEBUI_PORT (not WEBUI+PORT) as 8082. See here

Thanks that sorted it

[Rhodius]

Hi,

this forum in the past has helped me get my first Binhex-QbittorrentVPN container up and running. I've just setup and run the second container using the first's template and changing ports. As far as I can tell with the Linux torrent, it's working and I can see the downloaded file in progress. I had two questions though.

1. Anyone knows why Brave browser had error message "qBittorrent client is not reachable"? It works for the first Qbittorrent container, I had no issue whatsoever using Brave. For the second container/instance, only MS Edge/Firefox browser works though, the issue is only with Brave. Indeed I can't reach the config screen using Brave.

2. I must have followed some documentations somewhere which I couldn't find. I'm using PIA for VPN which I specify in the container setup, but how do I specify which VPN server and port forward or not to connect to? My first container is always using the same VPN server, the second one is always changing upon restart. 

 

Thanks.

[Rhodius]

12 hours ago, Rhodius said:

Hi,

this forum in the past has helped me get my first Binhex-QbittorrentVPN container up and running. I've just setup and run the second container using the first's template and changing ports. As far as I can tell with the Linux torrent, it's working and I can see the downloaded file in progress. I had two questions though.

1. Anyone knows why Brave browser had error message "qBittorrent client is not reachable"? It works for the first Qbittorrent container, I had no issue whatsoever using Brave. For the second container/instance, only MS Edge/Firefox browser works though, the issue is only with Brave. Indeed I can't reach the config screen using Brave.

2. I must have followed some documentations somewhere which I couldn't find. I'm using PIA for VPN which I specify in the container setup, but how do I specify which VPN server and port forward or not to connect to? My first container is always using the same VPN server, the second one is always changing upon restart. 

 

Thanks.

I found what I've done previously as far as fixing a VPN end point that I preferred, it was in the FAQ Q28/Q29. This is done through setting the Endpoint in user/appdata/binhex-qbittorrentcpn/wireguard/wg0.conf.

 

I still don't know why Brave wouldn't allow me access to the setting screen, only Edge and Firefox does that. Whenever I clicked on Option using Brave browser, it says "Error: n".

 

Thanks.

[Rhodius]

43 minutes ago, Rhodius said:

I found what I've done previously as far as fixing a VPN end point that I preferred, it was in the FAQ Q28/Q29. This is done through setting the Endpoint in user/appdata/binhex-qbittorrentcpn/wireguard/wg0.conf.

 

I still don't know why Brave wouldn't allow me access to the setting screen, only Edge and Firefox does that. Whenever I clicked on Option using Brave browser, it says "Error: n".

 

Thanks.

Not sure if this is a permanent solve, but using Edge I was able to access the option screen and then white-listed the internal IP range that I was using, and then I no longer get asked for user and password whenever I opened the Unraid server URL:XXXX. At the same time now Brave works and no longer gives me Qbittorrent is not reachable message as well as allows me to access the Option screen. 

[John Barlow]

@binhex Greetings,

I'm using the `binhex-qbittorrentvpn` container connected to PIA via Wireguard, and things have been mostly awesome.  I have a handful of other containers routed through it, but the one for Bazarr doens't want to start anymore.  I've traced the problem to a call to `raw.githubusercontent.com` ... The ssl handshake just hangs.  I connected my PC to the same PIA endpoint and was able to resolve it, so it's something with the container itself. 

You can run this from inside a container routed through the vpn to see what I'm talking about:

`curl --verbose -I --compressed https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/nvm.sh`

[LakersFan]

Hey all,

I'm trying to run sabnzbd to run through qbittorrentvpn and referring to ques #25 of the VPN Docker FAQ:

Container to route through VPN

    Left click icon and 'Edit' container and toggle advanced view (top right).
    In 'Extra Parameters' enter --net=container:<vpn container name>.
    Go to 'Network Type' and select 'none'.
    Remove all ports defined (no ports required as we will be accessing it via the vpn container).
    Click on 'Apply'.

Container running VPN

    Left click icon and 'Edit' container and toggle advanced view (top right).
    Click on 'Add another Path, Port, Variable, Label or Device' and add in a 'config type' of 'port'.
    Enter in the applications Web UI port for 'container port' and any non conflicting port number for 'Host Port' (host port must not be used by another container).
    Edit 'VPN_INPUT_PORTS' env var and put applications Web UI port number in the 'value', if multiple ports required then use a comma to separate.
    Click on 'Apply'.

 

The issue I am unclear on is under "Container to route through VPN" it says to remove all ports defined. Then under "Container running VPN" it says to enter the applications Web UI port for 'container port' and any non conflicting port number for host port. However the default port of sab is 8080, which is the port that qbit uses. Can someone help clear this up? Also, which port would I add under 'VPN_INPUT_PORTS'?

 

 

Edited March 30, 2023 by LakersFan
typo