I need to create an access log that can show who has accessed the airflow webserver. For example, when someone logs into an airflow webserver, then the username "User01" and the login time will be captured. Does any prodigy in stackoverflow have solved similar problem before? Thank you.
I can only find how to capture who has triggered the dag but not much information that capturing who has accessed the airflow webserver
You can activate the webserver access log by setting the config access_logfile to redirect the webserver log to a file.
You can change other configs in the webserver section to limit the events.
Related
Hello First of all I want to mentioned that I'm using Google cloud platform VM instance, openLiteSpeed + wordpress site.
I'm on fly more than a year with some domain and everything works well.
Today I bought a new domain and set it to my website and from this moment I can't enter to my site even if I'm using the External IP of my instance.
For now I deleted all my records in DNS section to try to handle this problem and still it does not work.
I also changed the virtual mapping on Listener section in openLiteSpeed dashboard.
I don't have idea what todo next, I try to solve this more than 5 hours.
Any suggestions how can I solve it ?
I reproduced your scenario in my own project-- I installed “openlitespeed-wordpress” solution.
I realised that this solution doesn't reserve an External IP, so when I stopped the instance and started it again, I wasn’t able to access my WordPress because my original IP was ephemeral, and it changed when I started my VM Instance again.
I solved this problem by modifying 2 fields in the DB, if you have the same issue you can follow the next steps:
In the Google Cloud Console, go to the VM instances page to check the new IP for your openlitespeed-wordpress Instance.
Use your new IP to access to your phpMyAdmin:
https://{Your-New-IP}/phpmyadmin/
If you don't know your credentials to access to phpMyAdmin you can get this information with the following command using ssh:
sudo sed -n 1p /home/ubuntu/.db_password
Once you have access, go to wordpress -> wp_options
Then you edit the option name
siteurl
home
After this action I was able to access my site again with my New IP.
To avoid this issue in the future you could reserve your IP:
In the Cloud Console, go to the VM instances page.
Click the name of the instance that you want to assign an external IP to.
The instance details page displays.
From the instance details page, complete the following steps:
a. Click Edit.
b. Under Network interfaces, click the edit button.
c. Under External IP, select Static external IP address to assign to the instance.
d. Click Done and Save.
Also I found some documentation that might help you to troubleshoot your issue.
I tried a lot, but couldn't deploy this cloudflare worker about bypassing the logged-in cache - https://www.mmaton.com/2018/07/02/cloudflare-cache-anonymous-requests/
or
Cloudflare service worker code to "Bypass cache on cookie" not working
Whichever may work. I am not sure how do I deploy this for a WordPress website? Added the script the in editor inside Cloudflare login, saved and exited and the cloudflare worker status remains zero, shows no activity.
Couldn't find any tutorial for deploying same for WordPress anywhere.
Can anyone help here regarding this?
Since you're not seeing any metrics for workers, it sounds like maybe the Worker script hasn't been enabled for any routes. In order for your worker to start processing requests, you'll have to configure route patterns that determine which requests should run the worker. To do so, navigate to the "Routes" tab next to the "Script" tab.
Then you'll need to click "Add Route". If you want to run the script for all requests to your site, you can use a route pattern like *example.com/* (replace example.com with your domain).
I have a running website (based on ASP.NET MVC) on some domain, let's say mydomain.com
Yesterday I was looking into site access logs and I noticed very weird logs: inside it, I saw different domain!
Something like anotherdomain.com/somePage
And I saw exception text in my log saying that 404 - anotherdomain.com/somePage can't be found. It looks like somehow my code running on some other domain (Request.URL show different domain).
How it is possible? Does that means that someone somehow got access to my host (I running on Azure) and steal my binaries and deployed on another host? Or maybe my website opened from iframe?
I need to understand in order to determine whether I have a breach.
If I had to guess, I would bet that someone accidentally set their domain's DNS records to point at your server. You can check where the A record for the domain is pointed with nslookup or whoisfrom the command line. If they are in fact mis-configured, you should contact the site administrator to let them know. This kind of mis-configuration, while uncommon, can happen more frequently with cloud services due to the inherently transient nature of the servers and routes used.
It's actually possible to make a GET request to access other domains, via your domain, to check if there's a badly configured proxy. Since you're not, it simply returns a 404 Not Found because you are not actually hosting those pages.
Scans like these happen all the time and is an unfortunate side effect of being connected to the internet, but does not mean that you are under attack or that someone has access to your host.
i have an website on wordpress, on an EC2 instance, with a ebs store, i access it using putty, and try to update the linux , cause its says updates where avaliable, it got a couple of errors in the process, and after that i couldn't access the website anymore, i check the instance status on my aws dashboard, and it says it could not be reached, try to reboot with no luck, then i stop it and start it, and works, both alerts was green, i try login with putty and works, however, when try to view the site using explorer it display a message "ERR_CONNECTION_REFUSED" , i read that after stop/starting a instance some settings has to be applied again, but the elastic ip addres its still the same, and the connection rules are still there, i guess its a setting that i have to make, but i have no clue, thanks. in advance
pd: even the website does not display at all, the favicon its shown, i access the instance via ftp using filezilla and works, all my flies are there.
I'm having a similar problem as was discussed in this question:
authClient.login returning error with "Unauthorized request origin"
I can't find anything on the firebase site that directly addresses this problem so I have 2 questions about the "unauthorized request origin":
1.) If I'm testing my program through my own computer (as in, it's just a file on my computer), what exactly am I supposed to add to the Auth panel? I tried following the advice offered in the link above but no luck.
2.) My eventual plan is to create an app using firebase and it's login system. Is this going to be a problem for when users try to login? Is there going to be something that I need to allow so that any user will be allowed to login to the system?
With the release of Firebase Simple Login, which contains a number of OAuth-based authentication methods (Facebook, Twitter, GitHub, etc.), we included the idea of 'Authorized Origins'. Without this restriction, malicious sites could pretend to be your application and attempt to access your users' Facebook, Twitter, etc. data on your behalf.
By restricting the domains for these requests to ones that you control and have verified, we can protect your users' data. Once you have configured your application domains, your users will be able to log in seamlessly and securely from the domains you defined.
To fix this error, log into Firebase Forge (by entering your Firebase URL into your browser), and navigate to the 'Auth' panel on the left.
For testing locally, you'll need to run at least a barebones webserver on your machine, rather than loading your test files via file://. The easiest way to run a barebones server on your local machine is to cd to the directory of your files and run python -m SimpleHTTPServer, which will allow you to access your content via http://127.0.0.1:8000/....
For your users, configure the domains that you'll be using to host your application. This can be any number of specific subdomains (such as a.b.www.domain.com) or high-level domains which will act as a wildcard (domain.com will allow requests from *.domain.com).
You can configure multiple application domains or IPs here, comma-delimited.
See https://www.firebase.com/docs/security/simple-login-overview.html for additional documentation about application configuration for Simple Login.
I hope that helps! Feel free to ping me directly if you have further questions.