Netlify deploy react application breaks on parameters - node.js

I am having trouble putting an app in production with Netlify. The app works smoothly locally, but when deploying to Netlify I am having trouble with this endpoint:
mywebsite.com/confirm?token=aaf21b43849e45d5576c6e8a3278d1c4&email=test#test.com
The page is directly not found.
If I enter
mywebsite.com/confirm?token=aaf21b43849e45d5576c6e8a3278d1c4&email=test#test
(without the .com) it works fine.
It seems like a Netflify bug/limitation, but I would like to confirm with a more experienced audience (you).
Thank you very much

My current workaround has been to encrypt the email and decrypt it again so no dots are in the URL. Not the best solution but it works.

Related

Unable to deploy a node.js / vue.js SPA online

I'm working on a project for adding an external pre-registration page with Stripe to a Wordpress website.
The wordpress is already in place. But the pre-registration page needed the Stripe module, working on back-end...
So I've decided to make a SPA outside this wordpress to have this pre-registrations set up for the next customers.
But now, I'm struggling from days to find how to put this project online, I may definitely need your help for that.
I have this file structure:
File structure
It's nothing more than a single page + a single css file and a single server.js file, that I need to start to interact with the Stripe API.
But I also need some modules like Stripe, which is the key function of this project.
I thought about bundling it with webpack (only the back-end, as the front is only composed of 1 html and 1 css file). Then upload it on my web host.
Haven't found any working way to do so.
I'd like to try some cloud services like Netlify, but I don't even think that it could work without bundling the server side
Everything works perfectly on localhost, but I'm absolutely unable to make it works in prod with a real domain name. And I'm already late to deliver it.
Do you have an idea on how I could do that?
Thanks

Why is Netlify changing my api link in the fetch request? Netlify: frontend Heroku: Backend

I launched my first fullstack application with Netlify and Heroku. When I test locally everything works fine but when I try the netlify I get this error in the terminal.
It should connect to Heroku, the fetch request is set up that way and I been looking online and can't seem to find any answer.
[Netlify][2]
[Front-end][3]
[Back-end][4]
P.s sorry for any odd formatting, stackoverflow insisted I format my code despite not writing any code

Problems with connection Node.js to React.js via env

I have created my fullstack (Node.js and React.js) blog app and now when I want to deploy my frontend and of course backend, I have noticed, that I don't know how to do it in a proper way.
My application works fine when I use localhost but if I deploy it, my links won't be like "localhost:8080/api/blablabla", but for example some heroku slug (url) and my Node.js routes.
In my Node.js it looks like this:
And here below my app.js code:
And from React.js (frontend side) it looks like this:
So, the question is what I need to add. I suppose, that on React (frontend) must me something like env. variables with backend link? And before it, better to add backend to know what the slug (url) would be, because it is random. But I dont know do I need to add something on backend or not.
If I wrote something wrong, I will be really appreciate if you correct me:)
ThanK you in advance
In the last React.js image you have shared, I can see you are using axios to send the GET request. However, you are providing a url which is a localhost one. So I assume you are trying to make a request to the backend that you have hosted on Heroku, but instead, the url is pointing to your local environment. What I would recommend doing is changing the http://localhost:5000 part to the Heroku app's url.

Node/React app with Auth0 runs fine locally but not on Heroku

I have a react app that I created with create-react-app. It runs fine locally and Heroku. I added Auth0. It ran locally fine. But on heroku, it run fine at home page, then I click on "sign in/sign up" button. It give me this DNS_PROBE_FINISHED_NXDOMAIN....
And I noticed in address bar.. the url they tried to use is...
https://undefined/authorize?redirect_uri=https%3A%2F%2Fsecret-taiga-61180.herokuapp.com&scope=openid%20profile%20e........(rest of text is deleted for brevity)
It seems Auth0 used https://undefined to start the authentication process. I know the undefined is an error. Suppose to be something else.
The sign on button worked fine locally. But on Heroku, it errorously go to https://undefined/....
Any idea?
I followed the tutorial from Auth0.com for React Login (using auth0-spa-js 1.0.0) exactly. It worked fine locally. I did input Auth0 config setting in Heroku Setting's config var. And everything else.
Still don't know where the 'https://undefined/' comes from.
Any ideas? anyone encountered this before?
My code is at: https://github.com/zenkbaries/react-heroku (it's in 'install-auth0' branch).
Let me know if you need more info.
thanks
John

Parse-server app not working gcloud

I have server based backend deployed on app engine and it's working(free trial), but it have too much resources. I want to deploy an updated version of it with more fine tuned app.yaml and some minor updates. The problem is: new version is not working. It have some redirect code and it works, when i directly type:
https://myapp/parse
it shows:
{"error":"unauthorized"}
it's all good.
But when i try to do login, or other CRUD it just writing logs and doesn't do anything.
Because of that all i can do is return traffic to old version, which is working just fine, and beg for help.
May be google did some updates in last month and i have to redo something in my app?
UPD
Backend always returns 307 redirect when i do authorized request, old(deployed in november 16) version works great.
It is not 100% clear for me the issue. If it is possible to show us the whole output.
But apparently, it is the HTTPS in your URL. Try it with HTTP. It is the most common scenario for the unauthorized error.

Resources