In addition to our Live website, we also have a staging and dev environment, the latter two of which both have .htaccess password authentication in place. I noticed that when I pull the staging or dev environment to my DevKinsta local, the .htaccess password is retained.
First of all, how do I disable it locally on these sites?
Secondly, is there a way to not copy the .htaccess config from these sites so that I don’t have to continually disable it when syncing environments?
Hi @juliaset
When pulling a Kinsta site (live or staging), it only pulls the site files and database. Any custom Nginx configurations are not pulled over to DevKinsta.
My guess is the Devkinsta Pull action isn’t able to fully replace all entries of your Kinsta Dev domain with the Devkinsta .local domain. The site uses the Elementor plugin, which seems to use an uninitialized class to manage the domain entries. If there are still Kinsta Dev domain entries left, this will still trigger the password authentication.
I suggest running a separate Search and Replace in your DevKinsta local site within Elemetor using the following:
Search: yourKinstaDomain.com (replace with your actual Kinsta domain)
Replace with: yourDevKinstadomain.local (replace with your actual Devkinsta domain)
Ref: Will Elementor Work If I Change The Domain Of My Website? » Elementor
I hope it helps; let us know how it goes.
Thank you! All fixed now. Yes, it was, in fact, some domain change search-and-replace that resolved the issue.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.