connecting to peers problem with bitcoin-qt

[sirstevie6]

Hi

I have downloaded and installed (as administrator) bitcoin-qt ver 0.18.1 (from bitcoin.org)

I am using Windows 10 (ver 1903) - all up date with windows update.

When I run bitcoin-qt it boots up and seems to hang and says connecting to peers. [I used bitcoin-qt a while back and it worked fine on this pc !]

I have included the contents of the debug.log file below - if anyone can offer me any help I would really appreciate that since I am keen to get back to running a full node again.

Thanks
Stephen

Here is the debug.log contents:


2019-10-27T08:56:37Z
2019-10-27T08:56:37Z Bitcoin Core version v0.18.1 (release build)
2019-10-27T08:56:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-10-27T08:56:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-10-27T08:56:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-10-27T08:56:38Z Using RdRand as an additional entropy source
2019-10-27T08:56:38Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2019-10-27T08:56:38Z Default data directory C:\Users\steph\AppData\Roaming\Bitcoin
2019-10-27T08:56:38Z Using data directory H:\backup of entire blockchain\new bitcoin area
2019-10-27T08:56:38Z Config file: H:\backup of entire blockchain\new bitcoin area\bitcoin.conf (not found, skipping)
2019-10-27T08:56:38Z Using at most 125 automatic connections (2048 file descriptors available)
2019-10-27T08:56:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-10-27T08:56:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-10-27T08:56:38Z Using 8 threads for script verification
2019-10-27T08:56:38Z scheduler thread start
2019-10-27T08:56:38Z Using wallet directory H:\backup of entire blockchain\new bitcoin area
2019-10-27T08:56:38Z init message: Verifying wallet(s)...
2019-10-27T08:56:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-10-27T08:56:38Z Using wallet H:\backup of entire blockchain\new bitcoin area
2019-10-27T08:56:38Z BerkeleyEnvironment::Open: LogDir=H:\backup of entire blockchain\new bitcoin area\database ErrorFile=H:\backup of entire blockchain\new bitcoin area\db.log
2019-10-27T08:56:38Z init message: Loading banlist...
2019-10-27T08:56:38Z ERROR: DeserializeFileDB: Failed to open file H:\backup of entire blockchain\new bitcoin area\banlist.dat
2019-10-27T08:56:38Z Invalid or missing banlist.dat; recreating
2019-10-27T08:56:38Z Cache configuration:
2019-10-27T08:56:38Z * Using 2.0 MiB for block index database
2019-10-27T08:56:38Z * Using 8.0 MiB for chain state database
2019-10-27T08:56:38Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-10-27T08:56:38Z init message: Loading block index...
2019-10-27T08:56:38Z Opening LevelDB in H:\backup of entire blockchain\new bitcoin area\blocks\index
2019-10-27T08:56:39Z Opened LevelDB successfully
2019-10-27T08:56:39Z Using obfuscation key for H:\backup of entire blockchain\new bitcoin area\blocks\index: 0000000000000000
2019-10-27T08:56:39Z LoadBlockIndexDB: last block file = 0
2019-10-27T08:56:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2019-10-27T08:56:39Z Checking all blk files are present...
2019-10-27T08:56:39Z Initializing databases...
2019-10-27T08:56:39Z Pre-allocating up to position 0x1000000 in blk00000.dat
2019-10-27T08:56:39Z Opening LevelDB in H:\backup of entire blockchain\new bitcoin area\chainstate
2019-10-27T08:56:39Z Opened LevelDB successfully
2019-10-27T08:56:39Z Wrote new obfuscate key for H:\backup of entire blockchain\new bitcoin area\chainstate: f9441dcaed4fd410
2019-10-27T08:56:39Z Using obfuscation key for H:\backup of entire blockchain\new bitcoin area\chainstate: f9441dcaed4fd410
2019-10-27T08:56:39Z init message: Rewinding blocks...
2019-10-27T08:56:39Z  block index             796ms
2019-10-27T08:56:39Z init message: Loading wallet...
2019-10-27T08:56:39Z BerkeleyEnvironment::Open: LogDir=H:\backup of entire blockchain\new bitcoin area\database ErrorFile=H:\backup of entire blockchain\new bitcoin area\db.log
2019-10-27T08:56:39Z [default wallet] nFileVersion = 180100
2019-10-27T08:56:39Z [default wallet] Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total. Unknown wallet records: 0
2019-10-27T08:56:39Z [default wallet] Performing wallet upgrade to 169900
2019-10-27T08:56:43Z [default wallet] keypool added 2000 keys (1000 internal), size=2000 (1000 internal)
2019-10-27T08:56:43Z [default wallet] Wallet completed loading in            3736ms
2019-10-27T08:56:43Z [default wallet] setKeyPool.size() = 2000
2019-10-27T08:56:43Z [default wallet] mapWallet.size() = 0
2019-10-27T08:56:43Z [default wallet] mapAddressBook.size() = 0
2019-10-27T08:56:43Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03T18:15:05Z' progress=0.000000 cache=0.0MiB(0txo)
2019-10-27T08:56:43Z mapBlockIndex.size() = 1
2019-10-27T08:56:43Z nBestHeight = 0
2019-10-27T08:56:43Z Failed to open mempool file from disk. Continuing anyway.
2019-10-27T08:56:43Z torcontrol thread start
2019-10-27T08:56:43Z AddLocal([2a00:23c4:6a83:4900:6ca0:e484:40b8:fe21]:8333,1)
2019-10-27T08:56:43Z Discover: DESKTOP-FPVT1VP - 2a00:23c4:6a83:4900:6ca0:e484:40b8:fe21
2019-10-27T08:56:43Z AddLocal([2a00:23c4:6a83:4900:852c:76e7:a79d:b737]:8333,1)
2019-10-27T08:56:43Z Discover: DESKTOP-FPVT1VP - 2a00:23c4:6a83:4900:852c:76e7:a79d:b737
2019-10-27T08:56:43Z Bound to [::]:8333
2019-10-27T08:56:43Z Bound to 0.0.0.0:8333
2019-10-27T08:56:43Z init message: Loading P2P addresses...
2019-10-27T08:56:43Z ERROR: DeserializeFileDB: Failed to open file H:\backup of entire blockchain\new bitcoin area\peers.dat
2019-10-27T08:56:43Z Invalid or missing peers.dat; recreating
2019-10-27T08:56:43Z init message: Starting network threads...
2019-10-27T08:56:43Z net thread start
2019-10-27T08:56:43Z addcon thread start
2019-10-27T08:56:43Z init message: Done loading
2019-10-27T08:56:43Z dnsseed thread start
2019-10-27T08:56:43Z Loading addresses from DNS seeds (could take a while)
2019-10-27T08:56:43Z 0 addresses found from DNS seeds
2019-10-27T08:56:43Z dnsseed thread exit
2019-10-27T08:56:43Z opencon thread start
2019-10-27T08:56:43Z msghand thread start
2019-10-27T08:56:43Z GUI: Platform customization: "windows"
2019-10-27T08:56:43Z GUI: PaymentServer::LoadRootCAs: Loaded  69  root certificates
2019-10-27T08:57:44Z Adding fixed seed nodes as DNS doesn't seem to be available.


Thanks for taking the time to look at this

[1715165449]

1715165449

[1715165449]

1715165449

[1715165449]

1715165449

[1715165449]

1715165449

[ranochigo]

Check your anti-virus and firewall if they are blocking connections. The client can't seem to even connect to the fallback nodes and it seems like something is blocking it.

Have you tried manually adding the nodes? Choose the IPs from bitnodes.earn.com and go to Window>Console and type in addnode (IP HERE) add. Replace the (IP HERE) accordingly.

[Rath_]

Your node can't connect to any of the DNS seed nodes which share the IP addresses of other Bitcoin full nodes. Do you have any firewall enabled and what are your Bitcoin Core startup parameters? You could try to mitigate this issue by manually connecting to a specific node for some time by adding '-connect=ip_address' to the startup parameters.

[sirstevie6]

Hi ranochigo

Thanks for coming back to me so fast.

I have tried disabling my anti-virus and also disabling the firewall - it makes no difference - I still get the same problem.

I had not heard of bitnodes.earn.com - interesting site - thanks for that.

I went to the windows console inside the bitcoin-qt program - however I am not exactly sure what to type in after addnode !!

Can you perhaps show me an example I tried addnode "80.238.125.164:8333" "add" - it said null - looks like it worked but nothing has changed!! - do I need the "add" parameter ?

Thanks four your help so far
Stephen





Check your anti-virus and firewall if they are blocking connections. The client can't seem to even connect to the fallback nodes and it seems like something is blocking it.

Have you tried manually adding the nodes? Choose the IPs from bitnodes.earn.com and go to Window>Console and type in addnode (IP HERE) add. Replace the (IP HERE) accordingly.

[ranochigo]

The command should be correct. Were you facing the same problem with your initial initialization of the client?

There were some instances whereby the client would refuse to connect to the peers due to a corruption in the loading of the database. Try backing up your wallet.dat and clear your data directory and try to synchronize the client again.

[sirstevie6]

Hi

An update on my situation.

I did manage to goto bitnodes.earn.com and found an node - I managed to add it to my bitcoin-qt startup as a parameter and it accepted it

It now says "1 active connection to the bitcoin network" - but it still appears to have hung.

I also changed my port from 9050 to 8333 in bitcoin-qt - since everyone else seems to be using 8333

Any thoughts on why bitcoin-qt (ver 0.18.1) is still in a hung state and saying "connecting to peers" !!!

Thanks
Stephen

[sirstevie6]

I have started from a fresh i.e. deleted the blockchain database folder contents and the the same for chainstate.

When I ran bitcoin-qt a while back (2 months ago) it worked fine!


Odd that it just connects to the 1 active connection I point it to and then seems to hang i.e. does not add more connections as it did in the past - still says 'connecting to peers' - any other thoughts/ideas more than welcome

[nc50lc]

2019-10-27T08:56:43Z ERROR: DeserializeFileDB: Failed to open file H:\backup of entire blockchain\new bitcoin area\peers.dat

Seems like you have an issue with your custom data directory.

Try to remove the spaces in the file/folder names of both "backup of entire blockchain" and "new bitcoin area".
Something like "blockchain_backup" and "new_bitcoin_area" will do, then set it as the new data dir.

[sirstevie6]

Just wanted to say 'thankyou' for helping me - believe it or not it seems to have helped a little!!

i.e. it have moved forward a bit and is now reporting "Synching Headers (0.00%)" and it is stuck there!
10 years and 42 weeks behind since I deleted all the data in chainstates and blockchain etc..

Is there anything else you can think of that I can try

I have reset my router and all ports including 8333 are open

Any help would be greatly appreciated

[sirstevie6]

Hi

I tried the windows compatability mode - I've used this before alas it did not help.

I live in the UK - I called BT (my ISP) and they said there are NOT blocking any ports.

Keep trying to eliminate things  - here is my latest log file - if anyone can help then I'd be so happy to hear from you :

Current problem is that the bitcoin-qt client on windows 10 is hanging at Synching Headers (0.0%) - never gets any further!
[I have tried emptying the blocks and chainstate folder - makes no difference!]

Here is the logfile: Help !

2019-10-27T20:44:53Z Bitcoin Core version v0.18.1 (release build)
2019-10-27T20:44:54Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-10-27T20:44:54Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-10-27T20:44:54Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-10-27T20:44:54Z Using RdRand as an additional entropy source
2019-10-27T20:44:54Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2019-10-27T20:44:54Z Default data directory C:\Users\steph\AppData\Roaming\Bitcoin
2019-10-27T20:44:54Z Using data directory H:\backup_of_entire_blockchain\new_bitcoin_area
2019-10-27T20:44:54Z Config file: H:\backup_of_entire_blockchain\new_bitcoin_area\bitcoin.conf (not found, skipping)
2019-10-27T20:44:54Z Using at most 125 automatic connections (2048 file descriptors available)
2019-10-27T20:44:54Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-10-27T20:44:54Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-10-27T20:44:54Z Using 8 threads for script verification
2019-10-27T20:44:54Z scheduler thread start
2019-10-27T20:44:54Z Using wallet directory H:\backup_of_entire_blockchain\new_bitcoin_area
2019-10-27T20:44:54Z init message: Verifying wallet(s)...
2019-10-27T20:44:54Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-10-27T20:44:54Z Using wallet H:\backup_of_entire_blockchain\new_bitcoin_area
2019-10-27T20:44:54Z BerkeleyEnvironment::Open: LogDir=H:\backup_of_entire_blockchain\new_bitcoin_area\database ErrorFile=H:\backup_of_entire_blockchain\new_bitcoin_area\db.log
2019-10-27T20:44:54Z init message: Loading banlist...
2019-10-27T20:44:54Z ERROR: DeserializeFileDB: Failed to open file H:\backup_of_entire_blockchain\new_bitcoin_area\banlist.dat
2019-10-27T20:44:54Z Invalid or missing banlist.dat; recreating
2019-10-27T20:44:54Z Cache configuration:
2019-10-27T20:44:54Z * Using 2.0 MiB for block index database
2019-10-27T20:44:54Z * Using 8.0 MiB for chain state database
2019-10-27T20:44:54Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-10-27T20:44:54Z init message: Loading block index...
2019-10-27T20:44:54Z Opening LevelDB in H:\backup_of_entire_blockchain\new_bitcoin_area\blocks\index
2019-10-27T20:44:55Z Opened LevelDB successfully
2019-10-27T20:44:55Z Using obfuscation key for H:\backup_of_entire_blockchain\new_bitcoin_area\blocks\index: 0000000000000000
2019-10-27T20:44:55Z LoadBlockIndexDB: last block file = 0
2019-10-27T20:44:55Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2019-10-27T20:44:55Z Checking all blk files are present...
2019-10-27T20:44:55Z Initializing databases...
2019-10-27T20:44:55Z Pre-allocating up to position 0x1000000 in blk00000.dat
2019-10-27T20:44:55Z Opening LevelDB in H:\backup_of_entire_blockchain\new_bitcoin_area\chainstate
2019-10-27T20:44:55Z Opened LevelDB successfully
2019-10-27T20:44:55Z Wrote new obfuscate key for H:\backup_of_entire_blockchain\new_bitcoin_area\chainstate: 63c8b54ebaafce41
2019-10-27T20:44:55Z Using obfuscation key for H:\backup_of_entire_blockchain\new_bitcoin_area\chainstate: 63c8b54ebaafce41
2019-10-27T20:44:55Z init message: Rewinding blocks...
2019-10-27T20:44:55Z  block index             652ms
2019-10-27T20:44:55Z init message: Loading wallet...
2019-10-27T20:44:55Z BerkeleyEnvironment::Open: LogDir=H:\backup_of_entire_blockchain\new_bitcoin_area\database ErrorFile=H:\backup_of_entire_blockchain\new_bitcoin_area\db.log
2019-10-27T20:44:55Z [default wallet] nFileVersion = 180100
2019-10-27T20:44:55Z [default wallet] Keys: 0 plaintext, 0 encrypted, 0 w/ metadata, 0 total. Unknown wallet records: 0
2019-10-27T20:44:55Z [default wallet] Performing wallet upgrade to 169900
2019-10-27T20:44:58Z [default wallet] keypool added 2000 keys (1000 internal), size=2000 (1000 internal)
2019-10-27T20:44:59Z [default wallet] Wallet completed loading in            3591ms
2019-10-27T20:44:59Z [default wallet] setKeyPool.size() = 2000
2019-10-27T20:44:59Z [default wallet] mapWallet.size() = 0
2019-10-27T20:44:59Z [default wallet] mapAddressBook.size() = 0
2019-10-27T20:44:59Z UpdateTip: new best=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 version=0x00000001 log2_work=32.000022 tx=1 date='2009-01-03T18:15:05Z' progress=0.000000 cache=0.0MiB(0txo)
2019-10-27T20:44:59Z mapBlockIndex.size() = 1
2019-10-27T20:44:59Z nBestHeight = 0
2019-10-27T20:44:59Z Failed to open mempool file from disk. Continuing anyway.
2019-10-27T20:44:59Z torcontrol thread start
2019-10-27T20:44:59Z AddLocal([2a00:23c4:6a83:4900:35a7:2ace:85db:5033]:8333,1)
2019-10-27T20:44:59Z Discover: DESKTOP-FPVT1VP - 2a00:23c4:6a83:4900:35a7:2ace:85db:5033
2019-10-27T20:44:59Z AddLocal([2a00:23c4:6a83:4900:852c:76e7:a79d:b737]:8333,1)
2019-10-27T20:44:59Z Discover: DESKTOP-FPVT1VP - 2a00:23c4:6a83:4900:852c:76e7:a79d:b737
2019-10-27T20:44:59Z Bound to [::]:8333
2019-10-27T20:44:59Z Bound to 0.0.0.0:8333
2019-10-27T20:44:59Z init message: Loading P2P addresses...
2019-10-27T20:44:59Z ERROR: DeserializeFileDB: Failed to open file H:\backup_of_entire_blockchain\new_bitcoin_area\peers.dat
2019-10-27T20:44:59Z Invalid or missing peers.dat; recreating
2019-10-27T20:44:59Z init message: Starting network threads...
2019-10-27T20:44:59Z net thread start
2019-10-27T20:44:59Z dnsseed thread start
2019-10-27T20:44:59Z addcon thread start
2019-10-27T20:44:59Z Loading addresses from DNS seeds (could take a while)
2019-10-27T20:44:59Z opencon thread start
2019-10-27T20:44:59Z msghand thread start
2019-10-27T20:44:59Z init message: Done loading
2019-10-27T20:44:59Z 0 addresses found from DNS seeds
2019-10-27T20:44:59Z dnsseed thread exit
2019-10-27T20:44:59Z GUI: Platform customization: "windows"
2019-10-27T20:44:59Z GUI: PaymentServer::LoadRootCAs: Loaded  69  root certificates
2019-10-27T20:45:19Z Socks5() connect to seed.bitcoin.sipa.be:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:45:39Z Socks5() connect to dnsseed.bluematt.me:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:46:00Z Socks5() connect to dnsseed.bitcoin.dashjr.org:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:46:00Z Adding fixed seed nodes as DNS doesn't seem to be available.
2019-10-27T20:46:20Z Socks5() connect to 2600:3c00::f03c:91ff:feb6:19f2:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:46:40Z Socks5() connect to seed.bitcoinstats.com:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:47:01Z Socks5() connect to 2604:a880:2:d0::22f8:f001:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:47:21Z Socks5() connect to seed.bitcoin.jonasschnelli.ch:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:47:41Z Socks5() connect to 2600:3c00::f03c:91ff:fe91:3e49:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:48:01Z Socks5() connect to seed.btc.petertodd.org:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:48:22Z Socks5() connect to 2a02:c207:2017:8175::1:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:48:42Z Socks5() connect to seed.bitcoin.sprovoost.nl:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:49:02Z Socks5() connect to 2001:0:9d38:953c:8a0:1fdb:ab00:bc2:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:49:22Z Socks5() connect to dnsseed.emzy.de:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:49:43Z Socks5() connect to 2002:2f5a:562a::2f5a:562a:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:50:03Z Socks5() connect to 2001:41d0:1004:18c7:::8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:50:24Z Socks5() connect to 2001:bc8:323c:100:::8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:50:44Z Socks5() connect to 2001:1af8:4070:a016:3333::5afb:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:51:05Z Socks5() connect to 89.230.96.42:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:51:25Z Socks5() connect to 204.15.11.4:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:51:46Z Socks5() connect to 2a02:c207:2017:1988::1:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:52:06Z Socks5() connect to 2001:41d0:1:5395::1:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:52:27Z Socks5() connect to 85.145.168.159:8333 failed: InterruptibleRecv() timeout or other failure

[Rath_]

2019-10-27T20:52:06Z Socks5() connect to 2001:41d0:1:5395::1:8333 failed: InterruptibleRecv() timeout or other failure
2019-10-27T20:52:27Z Socks5() connect to 85.145.168.159:8333 failed: InterruptibleRecv() timeout or other failure

What if you tried connecting via Tor to other nodes? You should find all the neccessary information here (running Tor as a service on Windows is described here in a more understandable way). All outgoing connections will go through the proxy.

[Foxpup]

I also changed my port from 9050 to 8333 in bitcoin-qt - since everyone else seems to be using 8333

Are you referring to your proxy setting? Because that setting doesn't refer to the port used by Bitcoin, but rather the port used by your proxy server. The setting is of no relevance if you're not using a proxy. In fact, if you intent to follow BitCryptex's advice and connect using Tor as a proxy, you'll need to change it back (9050 is the default setting because that's what Tor normally uses).

[nc50lc]

Just wanted to say 'thankyou' for helping me - believe it or not it seems to have helped a little!!

i.e. it have moved forward a bit and is now reporting "Synching Headers (0.00%)" and it is stuck there!
10 years and 42 weeks behind since I deleted all the data in chainstates and blockchain etc..
-snip-
I have reset my router and all ports including 8333 are open

Now, the dat files were successfully recreated, but the connection issue still persists.

Have you included any start-up parameter to your Bitcoin-qt/cli (or shortcut) before? If yes, try to start it normally by removing them.
You can also try to reset your "bitcoin.conf" (delete every line you've added) to try to launch it with default parameters.

This seems to be the issue:

I also changed my port from 9050 to 8333 in bitcoin-qt - since everyone else seems to be using 8333

Are you referring to your proxy setting? Because that setting doesn't refer to the port used by Bitcoin, but rather the port used by your proxy server. The setting is of no relevance if you're not using a proxy. In fact, if you intent to follow BitCryptex's advice and connect using Tor as a proxy, you'll need to change it back (9050 is the default setting because that's what Tor normally uses).

Because the advice written online is for your router, modem and firewall; not bitcoin-qt's proxy setting.