You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is likely some odd functionality concerning accessing local host 3000 while using Windows 10. The rails server will fail, due to https requirements of facebook. However, the thin ssl server will simply not appear for some windows users (myself). I tried a recommended route: 127.0.0.1:3000
That said, despite many suggestions for that, it did not work for me either. Possible workaround:
Run rails s [once it loads up, copy the address, something like example: 67.200.180.190:58100]
Close the rails s
Thereafter, run the 'bundle exec thin start --ssl'
Navigate to it using the previous rails server's address.
This worked for me, after acknowledging the unsafe warning that is expected for this lab.
The text was updated successfully, but these errors were encountered:
There is likely some odd functionality concerning accessing local host 3000 while using Windows 10. The rails server will fail, due to https requirements of facebook. However, the thin ssl server will simply not appear for some windows users (myself). I tried a recommended route: 127.0.0.1:3000
That said, despite many suggestions for that, it did not work for me either. Possible workaround:
Run rails s [once it loads up, copy the address, something like example: 67.200.180.190:58100]
Close the rails s
Thereafter, run the 'bundle exec thin start --ssl'
Navigate to it using the previous rails server's address.
This worked for me, after acknowledging the unsafe warning that is expected for this lab.
The text was updated successfully, but these errors were encountered: