I keep receiving an "Internal Server Error" redirect when I click the "Open Airflow UI" link in the Amazon MWAA console; it's just a blank white screen with "Internal Server Error" in big black text. I was being successfully redirected to the Airflow UI when I set up the environment, but it appeared to break overnight. It then started working again yesterday, then broke again today overnight.
Please let me know if I can provide further details--thank you!
I have tried and confirmed the following:
Region is correct with us-west-2
Logging in and back out as root user with access to everything
VPC setup and permissions are the same as when the Open Airflow UI was successfully redirecting me
VPC setup is with the standard AWS Cloudformation template that is provided during MWAA setup
A token is provided after the login = true portion of the URL redirect
Maintenance window is set as 7 AM UTC, Sunday, so it shouldn't be occurring now
I expect to be redirected to the Airflow UI successfully.
This is a bug that I expect to be fixed fairly quickly. As a workaround you can delete your browser's cookie whose name corresponds to your Airflow UI link, refresh, and you're good to go.
It is a known issue of MWAA. I am unsure what is the root cause of it, but I've seen this issue for a while. I am using MWAA Airflow 2.4.3. It happened when I tried to access MWAA Airflow UI the day after I deployed it.
You have to delete the cookie. I'll use Chrome to demonstrate it.
Open the Chrome Developer Tools and click Application then Cookie:
Click session and delete the value.
Now go back to AWS console MWAA environment page and click the Open Airflow UI button again, you should be able to access Airflow UI.
Hope this helps.
Related
I created my azure web-app and created app registration. and connected Azure AD to my web app. I used express security and I also used advance security with client ID and client secret. I know there is a similar question about this error. but it is not clear answer.
Most likely causes:
IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
IIS was not able to process configuration for the Web site or application.
The authenticated user does not have permission to use this DLL.
The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
Things you can try:
Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
Check the event logs to see if any additional information was logged.
Verify the permissions for the DLL.
Install the .NET Extensibility feature if the request is mapped to a managed handler.
Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
From your description, I know that the problem is most likely due to the lack of web.config file.
Solution:
It is recommended to ensure that your project can run normally locally.
Continuous deployment is recommended
At present, the reason for your problem is the lack of web.config, which will be automatically created when using git deployment. As shown below.
For more details, you can check my answer in another post.
Azure Web App getting “You do not have permission to view this directory or page.” when launch app
I'm trying to run a python script that interacts with the GMail Api on AWS EC2. Said script SHOULD either process the authenticated inbox or ask for authentication if the token doesn't exist. This authentication normally takes the form of opening up a browser window. This works on localhost but doesn't work on my EC2 instance.
I've tried running a webserver using Flask (accessible through its public IP) and having the call to the script be the result of clicking a button. When I do this, I get other interactivity from the Flask script and the authentication URL prints out on the CLI, but I'm not redirected.
I've tried just running the script from the CLI, but that obviously doesn't work. That last one might've just been desperation and/or wishful thinking.
EDIT: Info - The URL seems auto-generated so I don't know it ahead of time.
I'm trying to use bigrquery from an interactive R session for the first time. I've installed the R bigrquery package and successfully established a connection. I've authenticated following a redirect from the interactive RStudio session to the web browser for login, so oauth seems to be working correctly. However, when I try to run a query, such as DBI::dbReadTable(con, "A549_raw_merged_TADs")[1:6, ], I get the error Error: The project variant-annotation has not enabled BigQuery. [invalid].
I am sure I need to enable something else in the project on the Google side, but I'm not sure what I need to enable, or how to do that from the web console interface.
Is this documented anywhere, or can anyone here give me instructions?
Note: I have confirmed that the BigQuery API has Activation status of Enabled via the console at https://console.cloud.google.com/apis/api/bigquery-json.googleapis.com/overview, so although my question is the same as Error processing job: Project has not enabled BigQuery, the issue appears to be different.
Additional information: when I check the BigQuery API status via the console link above, there's a notification that "To use this API, you may need credentials. Click 'Create credentials' to get started."
So it may be that my assumption that oauth seems to be working is not correct.
You can enable the BigQuery API with this command gcloud services enable bigquery.googleapis.com, but, since you mention it is already enabled, you may be pointing to a different project.
Feel free to ping me on a new thread if you require assistance on the new issue.
This is the first time i am doing the deployment from my side and am new to AWS. I have a project deployed on Amazon AWS server for testing purpose. I have set the domain name as: https://domain.biz
I have a login page here where once the user logs in successfully i am setting the userId in the session and navigating the user to dashboard.
In the dashboard i have added a function to check whether session set with value of userId. If the session is not set then i am navigating user back to login page. This is to block the unauthorized access to site.
I am facing problem here. when i was working with the server before adding ssl it is working fine.after https://domain.biz session is working one page.and http://domain.biz works fine. When i have added domain to https then the session is not working. What is the problem here with AWS? Am i missing anything.
Check this : Session lost when switching from HTTP to HTTPS in PHP
Since codeignitor is in php, I suppose this thread could solve your issue.
I have free tier account(for about 5 months) for learning purpose and I cant see the s3 buckets. the page shows unexpected error. I have tried signout and sign in again but still, the same error is shown and also if I try to create a new bucket i cant create new bucket too, create button is disabled for me.i have pending bill of 50rs is this because of that? some one please help!!
I too have a free account with around 6 months left in it. I was able to access S3 bucket perfectly one day and was unable to do it later and got the same message as you. I looked at AWS forums and installed S3 browser and couldn't find any files with special characters.
When I looked at the console (in Chrome) it had lots of cross-origin request related errors; I found that I had installed a chrome extension Allow-Control-Allow-Origin: * (Description: Allows to you request any site with ajax from any source. Adds to response 'Allow-Control-Allow-Origin: *' header ). I just disabled this and the s3 buckets loaded perfectly from my chrome web browser.
To re-create the issue, I enabled this chrome extension again but no error came and the S3 buckets loaded normally.
I was facing same issue. Please try to deactivate CORS plugin (chrome) from your browser.