I am relatively new with deploying web applications so please bear with me!
I have successfully deployed a Flask API Backend on Heroku. I also have a frontend website and when I use localhost, the application communicates with the deployed API perfectly. However, when I deploy the frontend onto Heroku or AWS Amplify, it fails to communicate with the Backend API. Looking at the Heroku logs, it appears that it is not actually receiving the request so I was wondering how I would make it so that the frontend can communicate with the backend.
Related
my cli interface approval of my website deployment
when i run my website i get this
i deployed to the firebase server and expected the server to run my coded website but does not deploy
I have run the website but all i get is i should another from firebase hosting
Firebase Hosting Setup Complete
You're seeing this because you've successfully setup Firebase Hosting. Now it's time to go build something extraordinary! this is the message i get on my website instead of my html css and javascript code
I am trying to deploy my react app with a .NET Web API backend to IIS. In order to get the react app to show up I add the "homepage" property to my package.json for example "homepage": "/testapp/". The client app works and routes properly but any requests to the api just return the react app again instead of json data. When I launch the app locally in Visual Studio using IIS Express everything works fine. When I deploy the app all of api my routes for example /testapp/api/logs no longer return data (/api/logs returns 404). Does anyone have any insight on how to handle client side vs back end routing when deploying to IIS?
It was an issue with the connection to the data string. I added a test controller and found that the api was returning static data successfully. When it tried to hit the database it would return the index.html as an exception. I changed my site's authentication in IIS from anonymous to windows authentication and now my API returns data.
I am using a custom server with nextjs to inject some serverSideProps / getInitialProps into files. What I am doing is having something on the server update a json file every minute or so and then the getServerSideProps/getInitialProps functions read the json file from disk to populate data quickly (without having to do a network request for data).
Everything works great in localhost and when doing a build/running the build locally. In production / after deploying to vercel i get the error: Internal Server Error when trying to open a page. Vercel offers build logs but not any logs for the running custom server.
Is this likely a problem to do with unable to write to disk in the vm's that vercel uses to deploy apps?
Is there an example out there of how I can read/write to disk with a custom server in nextjs for this purpose?
Vercel is a serverless platform and doesn't support a custom server.
If possible, you can migrate away from the custom server (with API routes) or consider other hosting options.
Next.js Deployment
I have a scenario where I have an asp.net site with HTTP modules. I have another app built in angular 5 which needs to be hosted as a subsite of this site(This is plain angular).
I have tried deploying the site as an application in Azure app service. The subsite fails to load giving an error that it failed to load the HTTP modules. Is there a way to fix the issue for azure app service
I have tried setting the value runAllManagedModulesForAllRequests="false" but I does not fix the issue.
I have simple ASP.Net web app in which there is Socket connection implementation.
It is working in local IIS Server, but not working when deployed on Azure.
Source Code on GitHub.
It is working in local IIS Server, but not working when deployed on Azure.
I previously followed this tutorial to build my web application with WebSockets. Per my understanding, you need to enable the Web sockets option under the "SETTINGS > Application settings" of your Azure web App on Azure Portal. Moreover, here is a similar tutorial about Introduction to WebSockets on Windows Azure Web Sites, you could refer to it.
UPDATE:
For using SSL for WebSockets under Azure Web Apps, you could just connect to wss://{your-appname}.azurewebsites.net (WebSockets over HTTPS). Azure Web Sites supports SSL even on free sites by using a default SSL certificate for *.azurewebsites.net. Details you could follow this tutorial.
TEST:
Additionally, if it does not work in your web app, you could leverage the Log stream under the MONITORING section of your app service on Azure Portal to retrieve the detailed error message to narrow this issue.