When I try to import a website into a hosting space, the procedure fails.
No error is shown, but I found the following in audit log:
Could not import the web site because no dedicated IP address match in the target space has been found.
Please ensure the space has been allocated * IP address as a dedicated one and it is free. Then try to run import procedure once again.
This website was previously created in Solid CP under a different hosting space, and I am trying to transfer it to a different user.
Web service is configured with Web Sites Shared IP address: <All unassigned>
In IIS site bindings, the IP address is shown as either blank (port 443) or * (port 80), so it matches the <All unassigned> setting.
The system appears to be interpreting * as if it were a dedicated IP address.
Any suggestions? Thanks.
(I apologize this post is a duplicate. I think my previous attempt disappeared when I tried to include <special characters> in the title.)
Did you ever found a solution for this issue? I am exctly with the same message in audit log when I try to import any existing website!
No real solution. I think I ended up deleting the website from IIS and creating a new website in SolidCP.
I believe the Import Resource functionality is not working properly, because I created a new website using SolidCP 1.4.3, then I detached it and I tried to Import it again, but the same message showed up 🙁
Does it work if you make a test with a IP set and also configured in IIS Settings?
As the IIS Import does work on my live servers but they where set with an actual IP not *
I manually changed the bindings in IIS for my website, like:
The solidCP configuration like:
The Import Resource now is working for that website, but unfortnantly I can’t left the configuration in SolidCP like this, because when I create a new website the binding IP in IIS is set to a fixed one, I need it to be Unassigned.
Thank you for confirming that.
I would guess the import script check will need an adjustment for wildcard * to work with that properly, i will add it to the bug report.
Thank you for the answer!
Just for curiosity, how long will take until this bug get fixed and released? Would it be release in a minor version like 1.4.4?
This bug has been fixed and will be included in the next release.
- Views467 times
- Answers8 answers