Just binding to a given port does not mean that it can listen to Tor connections. In particular, if you do not have Tor running on port 9050 (and it sounds like you don't) then Core won't be able to send Tor traffic on port 18334 (which is always bound if you're using the equivalent of
-bind=address:port=onion in your configuration file or command line options.
The manpage says:
-bind=<addr>[:<port>][=onion]
Bind to given address and always listen on it (default: 0.0.0.0). Use [host]:port notation for IPv6. Append =onion to tag any incoming connections to that address and port as incoming Tor connections (default: 127.0.0.1:8334=onion, testnet: 127.0.0.1:18334=onion, signet: 127.0.0.1:38334=onion, regtest: 127.0.0.1:18445=onion)
So as you can see, it just flags connections to this IP/ports as Tor connections, but this does not mean it can actually connect to them.