I am using Rails 7.0.2.3 and my website is active for two weeks now. Devise gem for authentication.
Recently (today) one of my colleagues noticed a problem. When clicking on sign_out he is receiving 404 not found. He is using Safari on Iphone, I tested the same on Chrome on Samsung, and on browsers on Desktop PC
This is my View
<%= link_to 'Одјави се', destroy_admin_session_path, data: { turbo_method: :delete, turbo_confirm: 'Одјави се?' }, class: 'nav-link' %>
These are the logs I am catching from heroku.
2022-04-16T16:23:02.349221+00:00 heroku[router]: at=info method=GET path="/admins/sign_out" host=www.mywebsite request_id=********* fwd="**.**.**" dyno=web.1 connect=0ms service=4ms status=404 bytes=20331 protocol=https
2022-04-16T16:23:02.347534+00:00 app[web.1]: I, [2022-04-16T16:23:02.347453 #4] INFO -- : [*********] Started GET "/admins/sign_out" for **.**.**.** at 2022-04-16 16:23:02 +0000
2022-04-16T16:23:02.348459+00:00 app[web.1]: F, [2022-04-16T16:23:02.348405 #4] FATAL -- : [*********]
2022-04-16T16:23:02.348460+00:00 app[web.1]: [*********] ActionController::RoutingError (No route matches [GET] "/admins/sign_out"):
2022-04-16T16:23:02.348460+00:00 app[web.1]: [*********]
I will point out that this was not a problem until today, probably yesterday if we haven't noticed. How can something like this affect from sudden? I am able to sign_out from Desktop using Brave browser, both on normal mode and on Incognito.
Any advise could be useful.
Thanks
Related
I am new to Ruby and Rails in general and am following this series
https://gorails.com/episodes/rails-for-beginners-part-38-deploying-to-heroku
I have this weird issue where is everything seems to work fine except connecting my app with
Twitter Api.
I did everything to connect successfully but nothing seems working!
I added the website link to Twitter developer callbacks urls which are
https://jadwlh.herokuapp.com/
along with
https://jadwlh.herokuapp.com/auth/twitter/callback
I added both
API_KEY
and
API_SECRET
to Config Vars.
I even changed SECRET_KEY_BASE in Config Vars
to the one provided in the credentials file in my app!
Even though tried everything, still got this message shown in the image below when I try to
connect my app with Twitter Api
routes.rb file
# For details on the DSL available within this file, see https://guides.rubyonrails.org/routing.html
Rails.application.routes.draw do
#GET /about
get "about", to: "about#index"
get "password", to: "passwords#edit", as: :edit_password
patch "password", to: "passwords#update"
get "sign_up", to: "registrations#new"
post "sign_up", to: "registrations#create"
delete "logout", to: "sessions#destroy"
get "sign_in", to: "sessions#new"
post "sign_in", to: "sessions#create"
get "password/reset", to: "password_resets#new"
post "password/reset", to: "password_resets#create"
get "password/reset/edit", to: "password_resets#edit"
patch "password/reset/edit", to: "password_resets#update"
get "/auth/twitter/callback", to: "omniauth_callbacks#twitter"
resources :twitter_accounts
resources :tweets
# get "/", to: "main#index"
root to: "main#index"
end
Application logs
2021-05-31T06:15:04.415968+00:00 app[web.1]: [13f44544-8fd2-4348-8b08-1191ad53716b]
2021-05-31T06:15:04.418156+00:00 heroku[router]: at=info method=HEAD path="/auth/failure?message=session_expired&strategy=twitter" host=jadwlh.herokuapp.com request_id=13f44544-8fd2-4348-8b08-1191ad53716b fwd="217.182.175.162" dyno=web.1 connect=0ms service=3ms status=404 bytes=180 protocol=https
2021-05-31T06:15:31.243002+00:00 app[web.1]: I, [2021-05-31T06:15:31.242901 #4] INFO -- : [c5f8ff8c-58fa-439d-a9f3-e08047bc5aa8] Started POST "/auth/twitter" for 46.152.103.96 at 2021-05-31 06:15:31 +0000
2021-05-31T06:15:31.243645+00:00 app[web.1]: D, [2021-05-31T06:15:31.243583 #4] DEBUG -- omniauth: (twitter) Request phase initiated.
2021-05-31T06:15:31.388564+00:00 app[web.1]: E, [2021-05-31T06:15:31.388453 #4] ERROR -- omniauth: (twitter) Authentication failure! 400 Bad Request: OAuth::Unauthorized, 400 Bad Request
2021-05-31T06:15:31.390962+00:00 heroku[router]: at=info method=POST path="/auth/twitter" host=jadwlh.herokuapp.com request_id=c5f8ff8c-58fa-439d-a9f3-e08047bc5aa8 fwd="46.152.103.96" dyno=web.1 connect=1ms service=150ms status=302 bytes=834 protocol=https
2021-05-31T06:15:31.574904+00:00 heroku[router]: at=info method=GET path="/auth/failure?message=400+Bad+Request&strategy=twitter" host=jadwlh.herokuapp.com request_id=3adfd6f0-58b9-47c3-ab04-017161a56e18 fwd="46.152.103.96" dyno=web.1 connect=1ms service=6ms status=404 bytes=1902 protocol=https
2021-05-31T06:15:31.571195+00:00 app[web.1]: I, [2021-05-31T06:15:31.571067 #4] INFO -- : [3adfd6f0-58b9-47c3-ab04-017161a56e18] Started GET "/auth/failure?message=400+Bad+Request&strategy=twitter" for 46.152.103.96 at 2021-05-31 06:15:31 +0000
2021-05-31T06:15:31.572790+00:00 app[web.1]: F, [2021-05-31T06:15:31.572717 #4] FATAL -- : [3adfd6f0-58b9-47c3-ab04-017161a56e18]
2021-05-31T06:15:31.572791+00:00 app[web.1]: [3adfd6f0-58b9-47c3-ab04-017161a56e18] ActionController::RoutingError (No route matches [GET] "/auth/failure"):
2021-05-31T06:15:31.572792+00:00 app[web.1]: [3adfd6f0-58b9-47c3-ab04-017161a56e18]
Thank you: )
I found the solution.
It just was copying master.key and replace it as it says below!
heroku config:set RAILS_MASTER_KEY="copy and paste here config/master.key "
How to get rails master.key after upgrading to rails 5.2
Hi I'm fairly new to coding and I'm building a rails/react habit builder app. Everything works fine when running on local server. However I've switched the database over to postgres and deployed to heroku, and nearly everything works except for a create action in one of my of controllers.
def create
current_user.identities.build(identity_params)
if identity.save
render json: IdentitySerializer.new(identity).serialized_json
else
render json: { error: identity.errors.messages }, status: 422
end
end
here is my current_method
def current_user
#current_user ||= User.find(session[:user_id]) if session[:user_id]
end
here is the error in my heroku log
2020-11-16T16:14:03.944788+00:00 heroku[router]: at=info method=GET path="/api/v1/categories" host=atomic-habits-app.herokuapp.com request_id=94543abb-1522-464f-9c8e-44e7bc6f765b fwd="68.199.184.23" dyno=web.1 connect=1ms service=103ms status=304 bytes=445 protocol=https
2020-11-16T16:14:16.585828+00:00 app[web.1]: I, [2020-11-16T16:14:16.585700 #8] INFO -- : [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] Started POST "/api/v1/identities" for 68.199.184.23 at 2020-11-16 16:14:16 +0000
2020-11-16T16:14:16.587457+00:00 app[web.1]: I, [2020-11-16T16:14:16.587389 #8] INFO -- : [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] Processing by Api::V1::IdentitiesController#create as HTML
2020-11-16T16:14:16.587570+00:00 app[web.1]: I, [2020-11-16T16:14:16.587508 #8] INFO -- : [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] Parameters: {"identity"=>{"category_id"=>"1", "name"=>"test", "description"=>"test", "standard"=>"7"}}
2020-11-16T16:14:16.590058+00:00 app[web.1]: I, [2020-11-16T16:14:16.589975 #8] INFO -- : [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] Completed 500 Internal Server Error in 2ms (Allocations: 570)
2020-11-16T16:14:16.591415+00:00 app[web.1]: F, [2020-11-16T16:14:16.591334 #8] FATAL -- : [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b]
2020-11-16T16:14:16.591416+00:00 app[web.1]: [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] NoMethodError (undefined method `identities' for nil:NilClass):
2020-11-16T16:14:16.591417+00:00 app[web.1]: [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b]
2020-11-16T16:14:16.591417+00:00 app[web.1]: [f2c1ff5a-c6b8-4304-89a4-7174caed6c0b] app/controllers/api/v1/identities_controller.rb:17:in `create'
2020-11-16T16:14:16.592938+00:00 heroku[router]: at=info method=POST path="/api/v1/identities" host=atomic-habits-app.herokuapp.com request_id=f2c1ff5a-c6b8-4304-89a4-7174caed6c0b fwd="68.199.184.23" dyno=web.1 connect=0ms service=9ms status=500 bytes=1841 protocol=https
And again, this create action works perfectly fine when I run it on my local server. And in production the create method works for signing up a user and creating a session. And when creating a session I console.log the response from the sessions controller which includes
render json: {
logged_in: true,
current: current_user,
user: #user
}
And the current user object gets logged to the console upon login.
So im not sure if the issue is relationship related between identity and users (user has many identities), or if there is an issue relying on sessions in production? I've really made no progress debugging this. Any ideas or advice is very much appreciated. Sorry if I left out any necessary code. Here are links to repo and heroku
https://atomic-habits-app.herokuapp.com/
https://github.com/mattkuras/Habit-Helper
edit**
Thank you Eyeslandic for this response it seems to be working.
"Rails.application.config.session_store :cookie_store, key: '_habit-helper', domain: 'localhost:3000' could be the problem, referencing port 3000 especially"
I changed port 3000 to :all in my config/initializers/session_store.rb. The cookie wasnt properly being set
I apologize for this being a vague question but I don't know what is going wrong so I don't know how to ask the questions.
I set up a rails app and it's working locally. However, when creating it on Heroku Create and it gets set up on my Heroku server it does not work. When I run Heroku open I get this page:
https://polar-taiga-65467.herokuapp.com/
I can post logs or anything else to help. If someone can help me figure out what to do from here it would be appreciated.
Here is my GitHub project: https://github.com/TomTom319/morali-tee
Here is the log from Heroku:
2018-01-16T05:13:18.292500+00:00 app[web.1]: I,
[2018-01-16T05:13:18.292411 #4] INFO -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] Rendering simple_pages/index.html.erb within layouts/application
2018-01-16T05:13:18.295106+00:00 app[web.1]:
[99bf3dd0-59b3-4438-a3f7-36a037174b55] 3: 2018-01-16T05:13:18.293930+00:00 app[web.1]: I,
[2018-01-16T05:13:18.293863 #4] INFO -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] Rendered simple_pages/index.html.erb within layouts/application (1.3ms)
2018-01-16T05:13:18.294179+00:00 app[web.1]: I,
[2018-01-16T05:13:18.294089 #4] INFO -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] Completed 500 Internal Server Error in 15ms 2018-01-16T05:13:18.294881+00:00 app[web.1]: F,
[2018-01-16T05:13:18.294798 #4] FATAL -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] 2018-01-16T05:13:18.295107+00:00 app[web.1]:
[99bf3dd0-59b3-4438-a3f7-36a037174b55] 4: <%= image_tag("yellowtee", class: "img-responsive first-tee")%>
2018-01-16T05:13:18.295101+00:00 app[web.1]: F,
[2018-01-16T05:13:18.295028 #4] FATAL -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] 1: <h1 style="color:red;">MoraliTee</h1> 2018-01-16T05:13:18.295104+00:00
app[web.1]: [99bf3dd0-59b3-4438-a3f7-36a037174b55] 2: <p>Welcome! We are on a mission to give back to people around the world</p>
2018-01-16T05:13:18.295158+00:00 app[web.1]: F,
[2018-01-16T05:13:18.295086 #4] FATAL -- :
[99bf3dd0-59b3-4438-a3f7-36a037174b55] 2018-01-16T05:13:18.760114+00:00 heroku[router]: at=info method=GET
path="/favicon.ico" host=polar-taiga-65467.herokuapp.com
request_id=6a2ec4b7-7054-46b7-b76a-28ef5ab3f69a fwd="24.15.217.85"
dyno=web.1 connect=0ms service=2ms status=200 bytes=143 protocol=https
2018-01-16T05:13:18.293286+00:00 heroku[router]: at=info method=GET
path="/" host=polar-taiga-65467.herokuapp.com
request_id=99bf3dd0-59b3-4438-a3f7-36a037174b55 fwd="24.15.217.85" dyno=web.1 connect=0ms service=22ms status=500 bytes=1827
protocol=https
Simple_pages/index.html.erb code below:
<h1 style="color:red;">MoraliTee</h1>
<p>Welcome! We are on a mission to give back to people around the
world</p>
<%= image_tag("yellowtee", class: "img-responsive first-tee")%>
There was a file type missing from the end of my image on my simple_pages/index.html.erb page. I needed to .jpg to the end of my source in my image_tag.
Thank you #mmichael for your help in identifying the issue.
I thought there was something wrong with my db but I was incorrect. Thanks for your help.
I don't know where else to turn with this: I have spent many hours on my project, a recruiting events website for college students, but have reached quite the impasse.
In short, I plodded along in localhost - adding components like Devise; Omniauth authentication via providers Facebook, LinkedIn, and Google - building a website I was proud of along the way. Everything appeared to be working just fine, but once I pushed to 'heroku master' things started breaking big time.
I think the issues are most likely in or around:I have an Authentication model to keep track of a single user's authentication providers, alongside the User model (where all the oauth code is kept).
Without further ado, here is my app's heroku domain and my code:
http://lit-everglades-7633.herokuapp.com/
https://gist.github.com/mecampbellsoup/6357855
The things breaking which I suspect are related:
'heroku run rake db:seed' following 'pg:reset' & 'rake db:migrate'... instead of seeding with the contents of the seed file itself, a single blank Event and Company are created; more on this below
the routing and action relating to the omniauth request seems to be working just fine, according to the heroku logs (below) but no user nor authentication is actually created:
when, after resetting postgres db, I try to run 'heroku run rake db:create' or 'db:setup' I am whined at as follows:
☁ duke_recruits [master] heroku run rake db:setup
Running rake db:setup attached to terminal... up, run.5886
FATAL: permission denied for database "postgres"
DETAIL: User does not have CONNECT privilege.
also, 'heroku run rake db:seed' appears to be doing its thing, but then my db only has 1 empty Event and 1 empty Company:
☁ duke_recruits [master] heroku run rake db:seed
Running rake db:seed attached to terminal... up, run.1767
☁ duke_recruits [master] heroku run rails c
Running rails c attached to terminal... up, run.6135
Event.allLoading production environment (Rails 4.0.0)
irb(main):001:0> Event.all
=> #ActiveRecord::Relation [#Event id: 1, title: nil, location: nil, description: nil, date: nil, end_date: nil, company_id: nil, created_at: "2013-08-27 19:30:06", updated_at: "2013-08-27 19:30:06"]
irb(main):002:0> Company.all
=> #ActiveRecord::Relation [#Company id: 1, name: nil, description: nil, website: nil, logo: nil, created_at: "2013-08-27 19:30:06", updated_at: "2013-08-27 19:30:06"]
Logs (upon opening the app on heroku and trying google authentication):
2013-08-27T19:49:18.701285+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:49:18 +0000
2013-08-27T19:49:18.701019+00:00 app[web.1]: => Rails 4.0.0 application starting in production on http://0.0.0.0:49710
2013-08-27T19:49:18.701019+00:00 app[web.1]: => Ctrl-C to shutdown server
2013-08-27T19:49:18.701019+00:00 app[web.1]: => Booting WEBrick
2013-08-27T19:49:18.701019+00:00 app[web.1]: => Run `rails server -h` for more startup options
2013-08-27T19:49:18.701019+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:49:18 +0000
2013-08-27T19:49:19.131115+00:00 heroku[router]: at=info method=GET path=/ host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=2ms service=442ms status=304 bytes=0
2013-08-27T19:49:19.221284+00:00 heroku[router]: at=info method=GET path=/assets/application-b44a43097f814ac98347f6802323e25f.js host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=1ms service=12ms status=304 bytes=0
2013-08-27T19:49:49.440894+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:49:49 +0000
2013-08-27T19:49:49.440894+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:49:49 +0000
2013-08-27T19:49:49.515520+00:00 heroku[router]: at=info method=GET path=/ host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=2ms service=80ms status=304 bytes=0
2013-08-27T19:50:48.534099+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:50:48 +0000
2013-08-27T19:50:48.534099+00:00 app[web.1]: Started GET "/" for 68.175.76.48 at 2013-08-27 19:50:48 +0000
2013-08-27T19:50:48.575279+00:00 heroku[router]: at=info method=GET path=/ host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=1ms service=51ms status=304 bytes=0
2013-08-27T19:50:52.293922+00:00 app[web.1]: Started GET "/users/sign_up" for 68.175.76.48 at 2013-08-27 19:50:52 +0000
2013-08-27T19:50:52.293922+00:00 app[web.1]: Started GET "/users/sign_up" for 68.175.76.48 at 2013-08-27 19:50:52 +0000
2013-08-27T19:50:52.591752+00:00 heroku[router]: at=info method=GET path=/users/sign_up host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=1ms service=307ms status=304 bytes=0
2013-08-27T19:51:00.368352+00:00 app[web.1]: Started GET "/users/auth/google_oauth2" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.368352+00:00 app[web.1]: Started GET "/users/auth/google_oauth2" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.368926+00:00 app[web.1]: I, [2013-08-27T19:51:00.368823 #2] INFO -- omniauth: (google_oauth2) Request phase initiated.
2013-08-27T19:51:00.392262+00:00 heroku[router]: at=info method=GET path=/users/auth/google_oauth2 host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=3ms service=33ms status=302 bytes=469
2013-08-27T19:51:00.715597+00:00 app[web.1]: Started GET "/users/auth/google_oauth2" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.715597+00:00 app[web.1]: Started GET "/users/auth/google_oauth2" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.716822+00:00 app[web.1]: I, [2013-08-27T19:51:00.716706 #2] INFO -- omniauth: (google_oauth2) Request phase initiated.
2013-08-27T19:51:00.997866+00:00 app[web.1]: Started GET "/users/auth/google_oauth2/callback?state=40ecfd10739cb874b5c461fc00cfd72ec4fcb694ef3a6878&code=4/D_(omitted_for_security)_GBlmiYhY(partially_omitted)E9yth.QpxI3jdcGpYYshQV0ieZDAoQOqyCgQI" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.997866+00:00 app[web.1]: Started GET "/users/auth/google_oauth2/callback?state=10739cb874b5c461fc00cfd72ec4fcb694ef3a6878&code=4/D_GBlmiYhY1rCvgdgE9yth.QpxI3jdcGpYYshQV0ieZDAoQOqyCgQI" for 68.175.76.48 at 2013-08-27 19:51:00 +0000
2013-08-27T19:51:00.998508+00:00 app[web.1]: I, [2013-08-27T19:51:00.998379 #2] INFO -- omniauth: (google_oauth2) Callback phase initiated.
2013-08-27T19:51:02.188467+00:00 app[web.1]: Started GET "/users/sign_up" for 68.175.76.48 at 2013-08-27 19:51:02 +0000
2013-08-27T19:51:02.188467+00:00 app[web.1]: Started GET "/users/sign_up" for 68.175.76.48 at 2013-08-27 19:51:02 +0000
2013-08-27T19:51:02.234644+00:00 heroku[router]: at=info method=GET path=/users/sign_up host=lit-everglades-7633.herokuapp.com fwd="68.175.76.48" dyno=web.1 connect=9ms service=52ms status=304 bytes=0
Please let me know what questions you have for me and if I can clarify anything at all. I really appreciate your time & help SO!
After a pg:reset, you can run the create command, but it usually gives you output like:
slkdjfs0dslkd already exists
So then you'll know that your database is created and ready to be used. Before you can seed though make sure you migrate. Just the standard heroku way
heroku run rake db:migrate
Then seed as normal
heroku run rake db:seed
I'm developing a Rails App and am using Devise for authentication. For some odd reason, when my users sign up for the first time, it works perfectly fine, but after signing out and signing in again, the error "This website temporarily unavailable" pops up. This is really bizarre.
I am using the default Devise::SessionsController and the same create method for registration. Does anybody have any idea what's happening? Thanks so much for any help.
In my Application Controller I have the function
def after_sign_in_path_for(resource)
root_path
end
To redirect after sign-ins. Besides this I am using all the default Devise code.
UPDATE:
The error message "Website temporarily unavailable" shows up sometimes after following the link from the email.
Here's the code in the view:
<%= form_for(resource, :as => resource_name, :url => confirmation_path(resource_name), :html => { :method => :post }) do |f| %>
Could this be the source of the problem? Thanks a lot. Just as an aside I'm hosting on Heroku.
I checked the Heroku logs:
This is the result after registering:
Processing by RegistrationsController#create as HTML
2012-01-02T23:22:44+00:00 app[web.1]: Parameters: {"utf8"=>"✓", "authenticity_token"=>"brHjEOxwm4qhkuypmuIUohk0UVg+One8OUx6gsfvmgg=", "user {"email"=>"blah#blah.com", "name"=>"adsfasf", "password"=>"[FILTERED]", "password_confirmation"=>"[FILTERED]", "isartist"=>"0"}, "commit"=>"Sign up"}
2012-01-02T23:22:44+00:00 app[web.1]: Rendered devise/mailer/confirmation_instructions.html.erb (0.4ms)
2012-01-02T23:22:47+00:00 app[web.1]: Redirected to http://www.artinject.com/
2012-01-02T23:22:47+00:00 app[web.1]: Completed 302 Found in 2963ms
2012-01-02T23:22:47+00:00 app[web.1]: cache: [POST /users] invalidate, pass
And this is the result after sending the mail and clicking the confirmation link:
2012-01-02T23:22:47+00:00 app[web.1]: Sent mail to jw2896#barnard.edu (2755ms)
2012-01-02T23:22:47+00:00 app[web.1]: [paperclip] Saving attachments.
2012-01-02T23:22:47+00:00 heroku[router]: POST www.artinject.com/users dyno=web.1 queue=0 wait=0ms service=2982ms status=302 bytes=91
2012-01-02T23:22:47+00:00 app[web.1]:
2012-01-02T23:22:47+00:00 app[web.1]: Started GET "/" for 69.125.4.183 at 2012-01-02 23:22:47 +0000
Hopefully this helps. It doesn't look like heroku is throwing an error, although it says "Website temporarily unavailable"
I realize now why this was such a mystery. It turns out that GoDaddy was not forwarding my url consistently--sometimes it would properly forward my url and then other times it didn't. This explains why the Heroku logs were not throwing any errors.
Thanks for the responses everyone.