On 27 Apr 2018, at 08:23, Keifer Bly <keifer.bly@gmail.com> wrote:

My apologies. The fingerprint is DB1AF6477BB276B6EA5E72132684096EEE779D30

Here are the contents of my torc file (the isp beeng run from is Charter Communications, the only isp that is available where I live.

You might want to use a pastebin service for large files.
Or cut out all the commented stuff before posting your torrc.

I do not remember applying any descriptor limit and do not see one here.

The file descriptor limit is imposed by the OS.
The default can be low.

Here is how you can find out:

Please check the logs for warnings and notices.

Sometimes tor logs a warning when it starts up (for example, low file
descriptors), and then the issue happens later.

What’s strange is my internet connection is working fine and I am able to visit websites, making it not seem like it is overloaded.

Tor requires thousands of simultaneous connections.
Tor requires constant uptime.

Internet browsing requires a few connections.
It works when the network is interrupted.

Seems strange. Does Charter have any strange policies against running tor relays (has anyone ever had a documented here problem with running a relay on Charter before)? Thank you.

You should ask your ISP.

T