Motaz Shazly

No, it currently doesn’t support that feature, but we can consider it in the future.

That’s helpful to know @sterndata thank you, still, the fact that it doesn’t exist out of the box is a major security flaw in the plugins update setup and I think should be considered as a priority to fix in a following release soon.

I did disable all other plugins, and it worked again, I need to go through each to see which one is conflicting, will share an update accordingly FYI, I assume based on knowing the plugin you can potentially propose a fix, no?

Thank you,
Motaz

Hi @luckychingi I am having the same issue, checked PHP it’s 7.3 and curl, xmlreader, xmlrpc, and xmlwriter are installed, here is the error from the server:

GET /wp-admin/admin-ajax.php?action=wpaac_list_cdn&wpaac_ak=AKIXXXXXXXXXXXXT&wpaac_sk=Mw8XXXXXXXXXXXXXXXXXXXhyzmJDo&wpaac_ori=XXXX.XXXXX.com HTTP/1.0

AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Class ‘Aws\\CloudFront\\CloudFrontClient’ not found in /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-content/plugins/aws-cdn-by-wpadmin/aws-cdn.php:768\nStack trace:\n#0 /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-content/plugins/aws-cdn-by-wpadmin/aws-cdn.php(696): wpaawscdn->wpaac_authClient(‘AKIAYAP7ELVVAY7…’, ‘Mw8tYmSNAz//VTB…’)\n#1 /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-includes/class-wp-hook.php(288): wpaawscdn->wpaac_list_cdn(”)\n#2 /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(”, Array)\n#3 /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-includes/plugin.php(478): WP_Hook->do_action(Array)\n#4 /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-admin/admin-ajax.php(175): do_action(‘wp_ajax_wpaac_l…’)\n#5 {main}\n thrown in /var/www/vhosts/dev.XXXXXXX.com/httpdocs/wp-content/plugins/aws-cdn-by-wpadmin/aws-cdn.php on line 768\n’, referer: https://dev.XXXXXXX.com/wp-admin/admin.php?page=wpa-aws-cloudfront Apache error
2020-02-20 16:58:35 Access 172.68.94.169 200 GET /w

We’re running latest WP version and latest plugin version. Please let me know if you need more information of if the PHP class error is clear enough to fix, thank you.

Apologies for the late reply, we have updated tags, the plugin is compatible with version 5.3 of WP.

In relation to the error message, it is intentional that this specific error message can’t be deleted unless you follow what it says, basically this shows up after changing the permalink setup of your WP installation.
When that change happen you need to revise the plugin as it response automatically to the permalink change to maintain accessibility to dashboard, to further explain, If you’re using the default (non-friendly url) where your post URL is something like https://yourdomain.tld/?post=2352 and install the Secure AXS plugin, it follows that permalink structure so access login would be something like https://yourdomain.tld/?login, If you then change the permalink setup to use friendly URL, that login url will no longer work and it will automatically change to something like https://yourdomain.tld/login, and show that warning to make you sure you checked the new login url, it will then go away..Long story short. Follow the instruction in that message to maintain accessibility to your site and it will disappear. please let me know if you still have questions about that.

for your requests, I will look into when to squeeze that in as soon as I have a possible chance, thank you for using Secure AXS.

• This reply was modified 5 years, 10 months ago by Motaz Shazly. Reason: typos

Hi @wdalaa, Yes, the website is routed through cloudflare, but I have other websites running with that setup and not replicating the same issue. the website url is: https://cityandcountrycbt.com/ thank you.

@answersmode you MUST NEVER post the wp-config.php data publicly, you’re exposing your WP site to the public. please remove that file.

Glad you find it helpful, thank you for using the plugin : )

Hi Nicole,

First, I am so sorry for the late reply, glad you find the plugin useful, I am happy to help you with this issue, but to make sure I get it correct, you’re saying that you create the development site on a subfolder, so assuming it is something like https://yourdomain.com/wordpress_site/, then when you move the development site to live domain where it becomes (https://yourdomain.com) the plugin redirects you to the homepage instead of dashboard, yes?

If that’s the case, are you able to access the dashboard after you’re redirected to homepage? also after you do this, what is the access url from the plugin settings? is it updated or following the old subfolder setup?

Also, related to how you setup wordpress dev sites, I would recommend to use subdomains instead of subfolders, this way you easily maintain internal links within pages, easily migrate the site from dev to live without the hassle of updating .htaccess, ..etc. you can easily create subdomains and route them quickly using any reversed proxy (i.e Cloudflare) which also adds another layer of security and it’s free.

Hi Ramon,

The plugin adds security features to the login page that doesn’t exist by default and can not be removed like Google re-Captcha, and remove the option to remember username and password. Login will always be different from the default wordpress login screen.

You can however use the wordpress logo by uploading it to the logo fields. Also set the background color to the default one used by wordpress, but that’s how far you can go to make it look like the default wordpress login with logo/background.

Thank you.

Hi ramonjosegn, the new release ‘1.3.1’ is addressing the warning message you reported, please upgrade your plugin to the latest version to have that issue resolved, thank you.

Had the same issue, 4.5.2, thank you so much for pointing it out @julianm

Hi Ramonjosegn,

First, This is warning a not an error, the reason you’re seeing is due to bad configuration of PHP your server, I highly recommend changing the configuration to disable showing warning on site, this is a general recommendation not related to the plugin or the warning, you can easily resolve this by contacting your hosting service provider asking them to disable showing warnings on the site, once that configuration issue is resolved the plugin will work fine.

Second, If you’re unable to disable the configuration I will be releasing a newer version soon which will be addressing this warning issue you’re having, thank you for using the plugin.

Hi james, I am respecting that. thank you.

What if we need to contact to offer a free help?!