kerberoast spnroast over Socks5 TypeError

[Anders-Sec]

Attempting to spnroast through Socsk5 Proxy with the following command/URL:

sudo kerberoast spnroast 'kerberos+password://<Domain>\<User>:<Password>@<DC IP>/?proxytype=socks5&proxyhost=127.0.0.1&proxyport=4444' -t kerberoastable_spn_users.txt -o kerberoast.hashes

Receiving the following error:

Traceback (most recent call last):
  File "/usr/local/bin/kerberoast", line 33, in <module>
    sys.exit(load_entry_point('kerberoast==0.2.0', 'console_scripts', 'kerberoast')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/kerberoast-0.2.0-py3.11.egg/kerberoast/__main__.py", line 568, in main
  File "/usr/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/kerberoast-0.2.0-py3.11.egg/kerberoast/__main__.py", line 295, in amain
  File "/usr/local/lib/python3.11/dist-packages/minikerberos-0.4.1-py3.11.egg/minikerberos/common/factory.py", line 230, in from_url
    res.proxies = UniProxyTarget.from_url_params(url_str, res.port)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/asysocks-0.2.7-py3.11.egg/asysocks/unicomm/common/proxy.py", line 138, in from_url_params
    lastproxy.endpoint_port = int(endpoint_port)
                              ^^^^^^^^^^^^^^^^^^
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

I was able to Enumerate kerberoastable users with a similar command/URL through the proxy so it's not a networking issue.

I've tried using "kerberos+password-prompt" and a few other options during troubleshooting, for all of them I received either unknown protocol or the same error as above.

Running current Version from Github