# Connection refused - connect(2)

**URL:** <https://www.ruby-forum.com/t/connection-refused-connect-2/194811>\
**Category:** Rails\
**Created:** [September 11, 2010, 6:10am UTC](https://www.ruby-forum.com/t/connection-refused-connect-2/194811 "2010-09-11T06:10:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anthonys](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a3d4f5/32.png) [@anthonys](https://www.ruby-forum.com/u/anthonys)\
**Post date:** [September 11, 2010, 6:10am UTC](https://www.ruby-forum.com/t/connection-refused-connect-2/194811/1 "2010-09-11T06:10:12Z")

</div>

I got this error this evening while running my specs: Connection  
refused - connect(2)

I’m running under test/development and I’m using SQLite3. I didn’t have  
this issue yesterday and my code hasn’t changed since then. I looked  
around and people are saying that it’s a DB connection problem (which  
would make sense). However, I’m using SQLite3 so I don’t understand why  
it would have connection issues. I’ve restarted my machine, re-migrated  
my databases and nothing seems to work. The error comes up even if I try  
to do database operations manually in rails console.

I’m currently using Ruby 1.9.2 and Rails 3.0.0.

Any ideas?

---

<div class="post-metadata">

**Author:** ![anthonys](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a3d4f5/32.png) [@anthonys](https://www.ruby-forum.com/u/anthonys)\
**Post date:** [September 11, 2010, 7:06pm UTC](https://www.ruby-forum.com/t/connection-refused-connect-2/194811/2 "2010-09-11T19:06:12Z")

</div>

are you using rvm?

On Sat, Sep 11, 2010 at 12:09 AM, Anthony S.

---

<div class="post-metadata">

**Author:** ![anthonys](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/a3d4f5/32.png) [@anthonys](https://www.ruby-forum.com/u/anthonys)\
**Post date:** [September 11, 2010, 7:56pm UTC](https://www.ruby-forum.com/t/connection-refused-connect-2/194811/3 "2010-09-11T19:56:33Z")

</div>

It was a Sunspot issue. Thanks for the response though!
