Change DNS Manual to DNS API

See also questions close to this topic

• how to search for snapshots not equal to first day of the month aws command

  I just need to delete all the snapshots over 35 days but will retain all that is dated the 1st of the month. example June 1 2018, July 1, 2018 based on their StartTime here is my sample code.

  #!/bin/bash
  datecheck_35d=`date +%Y-%m-%d --date '35 days ago'`
  echo "$datecheck_35d"
  snapshots_to_delete=$(aws ec2 describe-snapshots --filters "Name=description,Values=created by awsbackup.sh*" --query 'Snapshots[?StartTime>=`2018-09-17` && StartTime!=`*17*` && ].{id:SnapshotId,time:StartTime}')
  echo $snapshots_to_delete > list.txt
  echo "List of snapshots to delete: $snapshots_to_delete"
  
  # actual deletion
  for snap in $snapshots_to_delete;
  do
          echo "--snapshot-id" $snap
          echo "aws ec2 delete-snapshot --snapshot-id" $snap
          #aws ec2 delete-snapshot --snapshot-id $snap
  done
  
• Unable to trigger Lambda function on S3 upload file event

  When I upload_file to S3 bucket I want it to trigger a lambda function. I don't see any related trigger options on lambda console. I tried POST, PUT and also Object Created (ALL), still it does't work.

  Can anyone help?
• AWS equivalent for Azure Resourcegroup

  Azure Resource group is one thing which ties one complete stack together, so in case you want to know what your complete stack looks like just open up your RG and all resources are there(not talking about very big stacks ). Do we have any service in AWS like this ??
• what ip numbers should mail-host DNS be when using mailgun?

  I have been using mailgun for inbound routing and needed to change some DNS configuration. In the A-section on the mail-host I found a strange IP-number that is not pointing to my server...

  What is the correct IP for the mail-host DNS when using mailgun? Please see attached screenshot.

  I am using lararavel forge -> digital ocean so the text says that on @ and www it is pointing to my droplet server. But on mail it is a mystery...

  
• Webpage not available The webpage could not be loaded because: Proxy Error

  I have a website which is hosted on Hostgator, it is giving error "Webpage not available The webpage could not be loaded because: Proxy Error" when loaded in browser. I tried to load it on different systems and it is still not working. I can see the HTTP status code as 502.

  Could anyone help in getting the website started again

  Thanks
• How can I connect my domain name to my wordpress site?

  Before I start, I searched a lot to solve my problem (and by a lot, I mean ... a lot) BTW sorry for my english

  Here is my problem: I have a Wordpress site, currently heberged at the following IP http://192.222.217.18 On this server, I use nginx, php7.0-fpm and mysql, everything was working fine

  Now, I bought a domaine name (at godaddy.com), this one: http://www.deals-with-it.com/ I "linked" it to my wordpress ip address (192.222.217.18) through the godaddy interface.

  After that I simply modified the home and siteurl parameter of wordpress to my new domain name. And ..... it didn't worked.

  Now when I try to access my wordpress blog from www.deals-with-it.com, it redirects me to my IP address 192.222.217.18 (I can see my adress in the address bar of the navigator, I don't want that), the CSS don't work, and all links are broken ...

  I think the problem come from nginx, but I already tried everything on this side ... I also purged wordpress and reinstalled it, same for the database.

  Here is the EXACT state of my my current platform:

  First of all, the godaddy DNS configuration

  enter image description here

  The IP is not the one I entered (192.222.217.18), but it seems to work anyway

  My nginx configuration /etc/nginx/sites-available/wordpress

  # Upstream to abstract backend connection(s) for php
  upstream php {
      server unix:/run/php/php7.0-fpm.sock;
      server 127.0.0.1:9000;
  }
  
  server {
      ## Your website name goes here.
      server_name www.deals-with-it.com deals-with-it.com;
      ## Your only path reference.
      root /var/www/wordpress;
      ## This should be in your http block and if it is, it's not needed here.
      index index.php;
  
      location = /favicon.ico {
              log_not_found off;
              access_log off;
      }
  
      location = /robots.txt {
              allow all;
              log_not_found off;
              access_log off;
      }
  
      location / {
              # This is cool because no php is touched for static content.
              # include the "?$args" part so non-default permalinks doesn't break when using query string
              try_files $uri $uri/ /index.php?$args;
      }
  
      location ~ \.php$ {
              #NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini
              include fastcgi.conf;
              fastcgi_intercept_errors on;
              fastcgi_pass php;
      }
  
      location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
              expires max;
              log_not_found off;
      }
  }
  

  (The socket /run/php/php7.0-fpm.sock exists) My wordpress /var/www/wordpress/wp-config.php file (only an extract that I modified)

  define('WP_HOME','http://deals-with-it.com');
  define('WP_SITEURL','http://deals-with-it.com');
  // Code for showing correct client IP address
  if ( isset( $_SERVER['HTTP_X_FORWARDED_FOR'] ) ) {
      $mte_xffaddrs = explode( ',', $_SERVER['HTTP_X_FORWARDED_FOR'] );
      $_SERVER['REMOTE_ADDR'] = $mte_xffaddrs[0];
  }
  

  I also added cgi.fix_pathinfo = 0; to my /etc/php/7.0/fpm/php.ini file

  I have nothing in my nginx logs, they are currently removed but I used to have logs defined in the file /etc/nginx/sites-available/wordpress, and nothing was wrong (no errors logged by nginx)

  I also modified the wordpress database to replace all 192.222.217.18 occurences to deals-with-it.com

  I honestly searched everywhere since yesterday, tried a lot of things, and I'm still stucked here, so if you could help me ...

  Thank you for your help

  Edit: I managed to have the righ address showing in the address bar of my navigator, by changing the IP into godaddy with the right IP, and I also changed the WP_HOME URL to define('WP_HOME','http://deals-with-it.com/wordpress'); But now I have 403 error for all my links
• Video Streaming using SSL on Alibaba ECS

  I have an ECS instance on Alibaba using LetsEncrypt for SSL configuration but i have an issue with PHP Video Streaming that is not working when SSL is used where Video Link gives 404 when the streaming begins but It works fine on http.

  This is the used package for streaming: http://codesamplez.com/programming/php-html5-video-streaming-tutorial

  And also this Package i already used and worked fine on another servers on https

  Can anyone advice what should i do?
• Let's Encrypt Certificate in Azure Web App for Containers with Custom Domain

  My goal is to create an Azure Web App for Containers, map a custom domain to it and secure this domain with an SSL certificate from Let's Encrypt which is automatically renewed every month.

  So far I have successfully configured a docker-compose for the web app:

  • Nginx which handles Let's Encrypt certificate renewals and https redirections
  • Web App to which Nginx proxies to

  Also, I successfully mapped my domain to the Azure Web App.

  But there is a problem. It seems Azure is applying some certificates on its own. When I want to use the Web App from my browser, the certificate for *.azurewebsites.net is served:

  

  Can I somehow disable SSL for the Azure Web App for Containers so that my Nginx proxy is responsible for this or use Let's Encrypt in some other way? I know that for the Windows-Based Web Apps there is a Let's Encrypt extension, but there is no one for Azure Web App for Containers.
• Let's Encrypt on Traefik with Helm

  I am trying to install Traefik as an Ingress Controller for my self-installed Kubernetes cluster. For convenience I try to install the helm chart of Traefik and this works excellent without the acme part; this is my variables yml now:

  externalIP: xxx.xxx.xx.xxx
  dashboard:
    enabled: true
    domain: traefik-ui.example.com
  ssl:
    enabled: true
    enforced: true
  acme:
    enabled: true
    challengeType: http-01
    email: example@gmail.com
    staging: true
    persistence.enabled: true
    logging: true
  

  Installed with:

  helm install --name traefik --namespace kube-traefik --values traefik-variables.yml stable/traefik
  

  But with helm status traefik I can see the v1/PersistentVolumeClaim named traefik-acme stays pending and the certificate is never assigned.
• Can't get SSL configuration working on Google Cloud Compute Engine

  I configured SSL for multiple Click to Deploy wordpress sites using the method found in this blog, here. It worked great for 3 of them however, when I go to set it up on this blog it completes the process but does not take. I've uninstalled Certbot and re-installed it. I've checked my chmod permissions and made sure most of the file structure is set to 777. I've restarted the server after all this, of course. Basically, is there some limitation within Certbot that I am unaware of that makes it unable to handle non dot-com domains? The URL is hosted in Google Domains. Is there an alternative method that I can try?
• Cannot connect to SSH after installing SSL cetificates through Certbot

  Recently I installed SSL cetificates through Certbot on apache2 server, and my website can be accessed through HTTPS. I have also enabled redirect to HTTPS. But I can no longer connect to the server via SSH. What can I do now?
• letsencrypt for port 81?

  I used certbot with LetsEncrypt and Nginx for my front-end site using the automated script and it worked great. However, I have my web service running on port 8090 and mapped to port 81. I can't connect to it from my https site b/c the web service isn't secured. I don't know how to update the config file for ssl with the web service (I'm not a devops guy). Can someone help? Here is my nginx config file for the web service.

  server {
      listen 81;
      server_name _;
      location / {
          proxy_pass http://example.com:8090;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection 'upgrade';
          proxy_set_header Host $host;
          proxy_cache_bypass $http_upgrade;
       }
  }