• Resolved davidsandbrand

    (@davidsandbrand)


    Has anyone experienced this before?

    I have a server that I own and have full root access on.
    Each site is in a docker container, and believes it’s the only site on the machine.
    Each site sees itself as located in /var/www/htdocs
    On one site, I can create a package with no errors.

    On a different site, the installer.php cannot see the archive. It’s there, it’s named correctly, and permissions are fine. I’ve even pulled the installer-backup.php from inside the archive, but no matter what I do, the installer cannot see the archive.

    I can create a new site on the same server, and the installer works fine – so I know it’s not a problem with duplicator, the archive, or the server. it’s the site.

    Can anyone explain what would cause this behaviour?

    Many thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hey @davidsandbrand

    It seems like there might be a path alias set up that is non-standard for the plugin to read. If you want to submit a support ticket for this issue we can have a closer look at your setup. Please provide a link to this thread when submitting the ticket.

    Thanks~

    Thread Starter davidsandbrand

    (@davidsandbrand)

    Hi @corylamleorg ,

    I actually just found out some info that I think explains it, and it may (not sure!) be a bug…

    So, I deleted the entire site and recreated it. Duplicator works.

    But I realized I forgot to put a cert on the site, so I deleted the site and recreated it with a cert. Duplicator doesn’t work.

    Then I deleted it and recreated it with no cert. Duplicator works again. Then I did the restore, and then added the cert.

    But here’s my thinking as to why…

    The site is in a docker container, and is running nginx.

    Then, the server is running nginx-proxy which is where all encryption is terminated. Then the proxy speaks to the site with http traffic – even if the site has a cert at the proxy layer.

    And so my thinking is that the installer.php script is grabbing the ssl status, and using that URL to fetch the archive. maybe? And since that traffic is actually happening inside the nginx instance, and there is no support for ssl, it fails. Probably getting a 404 error.

    Is that possible? Is the installer.php script actually doing something through the http/https protocol, instead of just locally with the files?

    The way I did it let me do this restore, but it won’t let me do it again, or move the site back, or anything like that. So my workaround is not even sustainable.

    FYI, the server is running https://easyengine.io/ – in case you want to test this yourself. There are some good diagrams on https://easyengine.io/handbook/internal/request-cycle that show the path of the traffic, if I haven’t explained it well.

    Hey @davidsandbrand,

    It can be tough to tell in situations like this. We run the plugin on mixed SSL sites all the time, so I’m not 100% sure, to be honest… If you would like us to have a closer look at your setup feel free to use the link above and we can try and isolate the issue for you…

    Thanks~

    Hey, just checking in to say a similar thing happened to me – sorry I’m too tired to sort out the differences right now. Bottom line is that on shared hosting with a (Let’s Encrypt FWIW) cert active, installation got as far as extracting the Duplicator files from the archive, then failed with a 500 error. After reading this post I decided to try installation again with the cert turned off and lo and behold it worked! So I installed the site, then reactivated the cert, added and ran the Really Simple SSL plugin, and everything is now perfect. I’m happy to share details if it would help, or post this to a new thread. Thanks @corylamleorg for a great plugin, and thanks @davidsandbrand for leading me to a really easy solution.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘installer.php cannot see archive, but it’s there’ is closed to new replies.