I am running my site on localhost as well as on a ...
# support-questions-legacy
b
I am running my site on localhost as well as on a webserver. On localhost, the following line works fine, but when deployed on a webserver, it throws a 404 redirectToAuth({ show: "signup" }); When I go to api.mydomain.com/auth/dashboard I am able to login with my API key but then I get this Server Error: Failed to load user list. Please refresh to try again. any ideas / suggestions? Thanks!
r
hey @bitcoinrippin . @nkshah2 can help
n
Hey @bitcoinrippin , Could you check the network tab in your browser and send us details about which API is failing?
b
Sorry that I don’t have access to a screenshot at this time.

https://cdn.discordapp.com/attachments/1104864661645561997/1105158406634999928/IMG_6471.jpg

I also have some CORS issues but I think that is unrelated.

https://cdn.discordapp.com/attachments/1104864661645561997/1105158709308559470/IMG_6472.jpg

this is what I get when navigating to /auth
I think I have another issue that could be causing this issue. When I navigate to https://development.bitcoinerfreelance.com/gig/18 using the buttons within the site (that use react router), I am taken to the page just fine. However, when I just copy paste that URL into a new tab, I get a 404 error as well.
Figured it out!!! I needed a .htaccess file with the following content: RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.html [L,QSA]
Thanks for being willing to help on this one guys, even though I was able to figure it out on my own.
I may have a different issue. When I sign up with a new account from my localhost session, here are the calls that are made:
but when I sign up with a new account from development.bitcoinerfreelance.com, here are the calls that are made:
r
Do you see any error stack on the backend related to the 500 error?
b
I’m going to have to implement error handling for that lol. Right now I just have console logs on the back end that we never visible. I’ll get back to you on that.
2 Views