I'm using Node-RED Starter to build my app. My app URL can be accessed here.
should appear on my browser, but I got an
instead.
The app however seems to be working fine on my dashboard. Can anyone point me in the right direction? Thank you.
Your app is throwing a 500 error which basically means that your app is very much broken. How did you build it? Which starter did you use?
As you are running in the IBM Cloud, I would drop what you already have, and recreate using the starter from the IBM Cloud catalog. Unless of course if that is what you used to create it in the first place. In which case as per the other suggestions look at the server side logs, from the options on IBM Cloud for your application.
Related
I recently deployed a Next.js application for a software engineering boot camp. I am using Vercel for hosting the web app. The problem I am having has been spoken about on the internet before. However, I couldn't find much helpful information.
When I look at the real-time logs for my application from my Vercel dashboard, a 504 error gets thrown for multiple API routes I have created. I am aware that Vercel places restrictions on requests depending on the hosting plan someone subscribes to. However, I can't help but wonder if I have overlooked an important step when deploying my application.
When deploying my application, I did the following things:
Connected a session store to my MongoDB database.
Created a password-protected MongoDB Atlas account (credentials are environment variables).
White-listed all IP addresses so that any user can interact with their portion of the database.
I would appreciate help finding out if these errors are my fault and if there is anything I can do about them or if they are solely caused by the restrictions of the "Hobby" plan.
Thank you very much in advance,
-Sam
Screen Shot:
I had a similar issue, turned out, it was just the fact that I did not add the vercel ip addr to the network access page on mongodb so momgodb was blocking vercel from accessing data.
You need to integrate MongoDB in your project on Vercel.
Go to your project settings in Vercel and go to the Integrations tab. Click the Browse Marketplace button and find MongoDb. Click Add Integration button and follow the instructions.
Hope this helps... I know this was asked quite a while ago.
You have to troubleshoot the issue by doing the following
Eliminate the NextJS app out of the equation - Using postman https://www.postman.com/downloads/ - Confirm the output of your API, what is the time the API takes? Given function invocation has a limit, you need to optimize the API to meet the threshold.
If the API times are fine and resolution occurs outside of your app, the next step is to troubleshoot the API route, remove the DB parts and just echo back a success message and check the function invocation time.
If #2 turns out to be the issue, reach out to vercel support - Another option could be hosting it outside and whitelisting the cross domain API ask from your application.
I have created a a new node serverless app (the lite one), created a DB in the associated cloudant service and clicked the download code button.
It spun for a while and then I got the following error
[SCAFF] Yeo generation failed due to error in generating a generator.
Anyone got a hint on how to debug/resolve please?
I'm just following the Knowledge guide to get familiar with the tooling.
Thanks,
M.
This is what I tried and worked.
I navigated to https://cloud.ibm.com/developer/appservice/apps and created a NodeJS + Cloudant serverless app in Washington DC region and I am able to download the code.
Alternatively, You can also download the app code from the CLI using the following command
ibmcloud dev code <APPLICATION_NAME>
#ibm,
I observed the slowness while running the Cloud Foundry app on Bluemix. Sometimes, it gets really irritated so when I tried to refresh the app, it even stopped the app which was very frustrating. Could you please let us know the root cause of this and is there any way to avoid this in future ?
Refreshing the cloud Foundry page has nothing to do with crashing of your app. Could you please provide some more details like:
Functionality you are trying.
Deployment Approach.
Whether the application is Liberty Java, NodeJS or something else.
And lastly your application logs. If you cannot copy directly from the logs, you can use the Log Analysis Service to copy the logs.
NOTE: I should have added this as a comment but I am still 35 reputation short.
I am trying to create an application in IBM Internet of Things Platform Starter and getting following message:
BXNUI0005E: The 'xxxxxx' app wasn't created because a problem occurred contacting Cloud Foundry.
Try again later. If you see this message again, go to the IBM Cloud status page to check whether a service or component has an issue. If the problem continues, go to IBM Cloud Support.
I've had exactly the same problem. It's usually because you've gone over the limit of app / database instances for your account.
In my case, I was using NodeRed. I created one instance successfully, deleted it, but then couldn't create another. It turned out that the first app had created an empty database instance and the second one was trying to do the same. Deleting the database from my dashboard resolved the problem.
We are using a MariaDB and a MongoDB (single instance) service in the Swisscom App Cloud.
If i try to create a backup with the backup button, it starts to create one, but fails after a few minutes.
Also, if i try to delete the failed entry, the deletion fails as well.
The interface provides no further information about the reason.
This happens for MariaDB as well as for MongoDB.
What could be a possible reason and how am I able to debug this error? Where can I get further information about the error?
screenshot of Portal:
Simon here from the App Cloud Team.
There was an issue in the backend which we fixed this morning, so your backups should now work again.
Sorry for the inconvenience.
I developed a CF CLI plugin for DB backups (MariaDB) in Cloud Foundry, called "cf-mariadb-backup-plugin", that also works in the Swisscom App Cloud. Check it out here, and give it a star. ;-)
If you use such plugin it presents the error message catch directly from the Cloud Foundry API. This might provide you, at least, better reasons on why such actions are failing.