I found A solution, but not what I hoped. I mean, it works but this is a professional product, free I know, but anyway, there is a lot of ppl with a lot of problems trying to maintain their portal alive while praying.

I had to rebuild 3 times the portal because of strange behavior (buttons disapearing, accounts deleted, etc.) As I explained before, all my files were the same, including web.config, so same keys.

So, why the hell couldn't dnn decrypt my already existing host password???

Solution: (Baaah, this is ugly and almost not a solution, sad to have to do joggling like this with production sites)

Just register a new user, then go to the table aspnet_Membership and replace the password and the salt of host by the new registered user value.

To check which user is the new one, check the user id value against the aspnet_Users table.

Im sure I did something that made dnn get mad, I take all the responsability for what happened, I'm not saying it doesn't work. I just say that it is too much easy to break it and I think that as a professional, I am really afraid as I see that the product isn't still stable as it should.

Anyway, maybe this could help someone.

Lorenzo.