I am facing a very unusual error. When a user clicks on the button the website sends an AJAX request, which adds some data in the PHP SESSION structure. After the successful AJAX call returns the page is redirected to another page. Some times the AWS Load Balancer redirect the user to another AWS instance of the website. When the user lands on the redirected page the SESSION structure has some missing data. Which breaks the website user flow.

Why each instance has different SESSION ID even though it is part of the same user instance on the website. And why there is a missing SESSION structure when the AWS automatically switch the users between the 2 instances.

How can I fix this issue? Please advise and support regarding this matter. I will really appreciate any help.

Thank you,

We are trying to run a simple WP site, that uses the Plugin of WP Offload Media. The site is running on an EC2 instance with instance metadata service version 1, and connects to a S3 bucket. Currently the plugin is configured to use the EC2 instance role. For sec reasons, we need to implement instance metadata service version 2, which requires a previous call to retrieve a token and then a call to the metadata endpoint.

with IMDV1:

curl https://169.254.169.254/latest/meta-data/

with IMDV2:

TOKEN=curl -X PUT “https://169.254.169.254/latest/api/token” -H “X-aws-ec2-metadata-token-ttl-seconds: 21600” \
&& curl -H “X-aws-ec2-metadata-token: $TOKEN” -v https://169.254.169.254/latest/meta-data/

Doc here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html

We have been trying to sort this out but we weren’t able; any insight on this? The creation of a user for this purposes isn’t approved, so we need to use ec2 instance role.

Thanks!

We are trying to run a simple WP site, that uses the Plugin of WP Offload Media. The site is running on an EC2 instance with instance metadata service version 1, and connects to a S3 bucket. Currently the plugin is configured to use the EC2 instance role. For sec reasons, we need to implement instance metadata service version 2, which requires a previous call to retrieve a token and then a call to the metadata endpoint.

with IMDV1:

curl https://169.254.169.254/latest/meta-data/

with IMDV2:

TOKEN=curl -X PUT “https://169.254.169.254/latest/api/token” -H “X-aws-ec2-metadata-token-ttl-seconds: 21600” \
&& curl -H “X-aws-ec2-metadata-token: $TOKEN” -v https://169.254.169.254/latest/meta-data/

Doc here: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html

We have been trying to sort this out but we weren’t able; any insight on this? The creation of a user for this purposes isn’t approved, so we need to use ec2 instance role.

Thanks!

My AWS instance is running again, but I can’t reach the site. Even if I click on and open “public IPv4 address” shown in the instance I get this error “Hmmm… can’t reach this page <<my_site_ip_adress>> refused to connect.”
I noticed IP address has changed. Not only that it is not available over browser.

When I type in the address in the browser, I get this error:

“This site can’t be reached www.my-site.com refused to connect. Try:

Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED”

For obvious reasons, this is <span style=”text-decoration: underline;”>very critical. </span>
Main question is – is my WordPress site still there, and if yes – how exactly can I get it back?
Has anybody gone through this (horrible) experience? What changes and what needs to be done to get the site up again?
(URGENT)

Thanks in advance!

When I run: /opt/bitnami/php/etc# /usr/bin/php.default -v
PHP 8.2.1 (cli) (built: Jan 13 2023 10:43:08) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.2.1, Copyright (c) Zend Technologies
with Zend OPcache v8.2.1, Copyright (c), by Zend Technologies

But when I run :/opt/bitnami/php/etc# php -v
PHP 7.3.17 (cli) (built: Apr 23 2020 08:07:47) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.17, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.17, Copyright (c) 1999-2018, by Zend Technologies

I feel I tried everything! Seems the new PHP is installed but is not taken into account.

Does anyone have any idea?

Old Site – Lightsail
WordPress version: 5.7.2
MySQL Version: 8.0.20
PHP Version: 7.3.18

New Site – Testing locally with Docker Compose
WordPress version: 5.7.2
MySQL Version: 8.0.25
PHP Version: 7.4 (also tried with 8.0)

I was able to Export the data from the old website with AIO WP Migration plugin to backcup.wpress (260M).

I configured the memory_limits in /var/www/html/.htaccess to

# BEGIN WordPress

RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

php_value upload_max_filesize 2000M
php_value post_max_size 2100M
php_value memory_limit 2100M
php_value max_execution_time 600
php_value max_input_time 600

I installed the All-in-One WP Migration plugin v7.44 on the new website and attempted to Import my backcup.wpress (260M) file.

The result – Restoring database... stuck on 91%, if I try multiple times (on a fresh new website each time) I sometimes get to 93%, but that’s it. I even got once to Done restoring database, but it was still stuck with a forever spinning snipper.

Logs of the WordPress server (a lot of them)

[Sat Jun 19 20:29:19.036912 2021] [php7:error] [pid 59] [client 172.28.0.1:52768] PHP Fatal error:  Allowed memory size of 2202009600 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/wp-includes/wp-db.php on line 1370, referer: https://mysite:8000/wp-admin/admin.php?page=ai1wm_import

I’m trying to test everything locally with Docker Compose, here’s my docker-compose.yml

version: "3.9"
    
services:
  db:
    image: mysql/mysql-server:8.0.25
    volumes:
      - db_data:/var/lib/mysql
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: somewordpress
      MYSQL_DATABASE: wordpress
      MYSQL_USER: wordpress
      MYSQL_PASSWORD: wordpress
    
  wordpress:
    depends_on:
      - db
    image: wordpress:5.7.2-php7.4 # Also tried with php8.0
    volumes:
      - wordpress_data:/var/www/html
      - ./.htaccess:/var/www/html/.htaccess
    ports:
      - "8000:80"
    restart: always
    environment:
      WORDPRESS_DB_HOST: db:3306
      WORDPRESS_DB_USER: wordpress
      WORDPRESS_DB_PASSWORD: wordpress
      WORDPRESS_DB_NAME: wordpress
      WORDPRESS_DB_CHARSET: utf8
volumes:
  db_data: {}
  wordpress_data: {}

Any suggestions on how to fix this? I’ve tried playing with values in .htaccess with not luck.

Also important to mention, I have to delete the new WordPress website when it gets stuck during the Import process. Seems like the whole website gets corrupted and the server is not responding anymore, even after a restart.