Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby

Eddie Flores
Eddie Flores
9,110 Points

After installing Devise - [Solved]

I'm going through this tutorial for the 10th time. This time around I'm getting an issue to where if I go to /users/sign_up or /users/sign_in or after I create a status, it gets redirected to the localhost WITHOUT the port.

The first time I was able to get to users/sign_up and register. Immediately after, it went back to the localhost with no port associated.

Started GET "/users/sign_in" for 66.00.000.000 at 2013-10-09 14:52:56 +0000
Processing by Devise::SessionsController#new as     HTML
User Load (0.3ms)  SELECT "users".* FROM "users" WHERE "users"."id" = 1 LIMIT 1
Redirected to http://myrubybox-39196.use1.actionbox.io/
Filter chain halted as :require_no_authentication rendered or redirected

That's pretty much what I get. I'm using a box I've set up with Nitrious.io. It's worked every other time that I've used it. The only difference I've made this time around is that I have started with RVM, using Ruby 1.9.3 and Rails 3.2.12. In hopes that it might work correctly.

If I post something, it doesn't go to the confirmation of the status, but when I go back to the index it shows that it was done. It just redirected me to the wrong place.

How can I fix this? I've looked online and there were some ideas, but I don't want to go too off book for this one.

Eddie Flores
Eddie Flores
9,110 Points

Nevermind. Figured it out. I resolved this by going to /users/edit and changing my password. I imagine that by doing that it reset something in the confirmation that it wasn't getting before, but now is.

It was a long-shot solution I randomly saw and it worked.

1 Answer