I am trying to deploy my nuxt site on Netlify, it is deployed But I am facing some issues with environment variables. When I try to log in to the site, it's working correctly & moves to the index page. But when I am trying to search for something on the nuxt app the API fails due to an undefined environment variable even if I am using the same environment variable for the login API call. I am adding the environment variable here.
It's the successful API call with environment variables,
It's the unsuccessful API call with the same environment variables. Its also embedded in the other domain at the start of the API call.
Related
I'm trying to use the Sendgrid email API to send messages via a form. I have the API key stored in an .env.local file that works fine locally.
But when I deploy it on Vercel it stops working. I've added it in my environment variables on the site dashboard on Vercel with the same title and value as it appears locally.
The site is on Vercel over here:
https://forward-dev.vercel.app/find
I don't really know where to begin debugging it. Any help appreciated.
I've recently moved a Rails 6 web application to Azure Web App service using Linux from an AWS Elastic beanstalk environment. I'm having an issue with a particular URL, when searching the following link:
www.website.com/link/asd%2Fasw
I get a 404 error. In my browser the link remains as www.website.com/link/asd%2Fasw, but in myWeb App service logs it decodes the URL to:
www.website.com/link/asd/asw
Hence why we get the 404 page error. I'm unsure of why this is happening. In our AWS environment the logs recorded the link as www.website.com/link/asd%2Fasw and everything was working as it should.
I have tried modifying the web.config file, but have been told that being a Linux environment this file is not supported (unsure of if this is correct).
I am working to migration a rails app from its current PaaS to aws elastic beanstalk. Everything went well except that elastic beanstalk allows configuration to have key and value combined max 4096bytes in size. As my app has many third parties api credentials making my config way bigger than 4096bytes.
I found an excellent service in AWS for storing secret credentials called AWS System Manager Parameter Store to overcome the 4096byte limitation.
My goal is to store my credentials and then load them back in to ENV variable for my application, however I found the following problems:
How to be able to separate the config value for different env, in my case I will have a staging and a production in parameter store? Do I need to duplicate the key for each env? what is the practice of organizing those keys to be able to easily load into ENV var programmatically?
How to be able to access the parameter store en it current env accordingly? i.e when the container get deployed in production env the parameter store values in production should be loaded ENV var but not those in staging.
What are the best practices to allow ElasticBeanstalk instance to access AWS system manager parameter stores via AWS IAM?
I tried a few commands in AWS CLI to read and write locally, it works well for example something like this
aws --region=us-east-1 ssm put-parameter --name STG_DB --value client --type SecureString
aws --region=us-east-1 ssm get-parameter --name STG_DB --with-decryption --output A --query Parameter.Value
I need some standard procedures or practices that people do to solve all the above problems.
Step by step guide and example will be very useful.
Hello I've followed so far the tutorial https://developers.sap.com/tutorials/s4sdk-odata-service-cloud-foundry.html
step by step and I'm having issues, to run the solution on local machine.
I'm running windows 10 and according to tutorial I have set an environment variable to be as following:
destinations=[{name: "ErpQueryEndpoint", url: "xxxx.s4hana.ondemand.com", username: "INT_USER", password: "xxxxxxxx"}]
when i run the solution on localhost i get this:
Message Error occured while handling request: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: Failed to get destinations of provider service instance: Failed to get access token for destination service. If your application is running on Cloud Foundry, make sure to have a binding to both the destination service and the authorization and trust management (xsuaa) service, AND that you either properly secured your application or have set the "ALLOW_MOCKED_AUTH_HEADER" environment variable to true. Please note that authentication types with user propagation, for example, principal propagation or the OAuth2 SAML Bearer flow, require that you secure your application and will not work when using the "ALLOW_MOCKED_AUTH_HEADER" environment variable. If your application is not running on Cloud Foundry, for example, when deploying to a local container, consider declaring the "destinations" environment variable to configure destinations.
Be sure to set the destinations variable so it is visible to your application. You can check using System.getenv("destinations"); in your code.
Getting following error,
An error occurred while processing your request. Request ID:
0HLIETLEOHKHF:00000003
Development Mode
Swapping to Development environment will display more detailed information about the error that occurred.
Development environment should not be enabled in deployed applications, as it can result in sensitive information from exceptions being displayed to end users. For local debugging, development environment can be enabled by setting the ASPNETCORE_ENVIRONMENT environment variable to Development, and restarting the application.
I have code something asp.net core mvc crud actions and it runs with iss properly but when i publish it with azure; the homecontroller(default visual studio thing) is ok. But my newly controller errors like that.
You can set environment variable in App service configuration, then application settings.
Add the ASPNETCORE_ENVIRONMENT variable and set value and restart the app service.