Sign in

Problem with multiple netlify accounts

  • This topic has 6 replies, 3 voices, and was last updated 2 months, 2 weeks ago by .
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #5755
    Jampi

    I have two websites on the publii app, each of one belong to different netlify accounts.

    When I set APP ID and token to the first website it automatically apply to the second, so I update the credentials of the second, but then the first one’s credentials change to the ones of the second…

    What can I do to stop this?

    #5771
    Jampi

    UPDATE 07/05/2021

    I checked the site config, I think that te probles is that the sites have the same “uuid”.

    So I tried this:

    1. I deleted all netlify API IDs anc Tokens from all websites
    2. Duplicated one of the websites

    After doing that I checked the uuid and they were different.

    So I added netlify API IDs and Tokens again, but after I do this, the uuids of both websites match again.

    Is it a bug? If someone else can confirm I’ll submit the issue to github.

    For now I’ll simply insert API ID and token every time I switch site.

    #5773
    Jampi

    Another Edit:

    I added a new website, and deployed to netlify with other custom token and ID. It works well and access credentials do not override with other sites.

    I think this problem occours only with duplicated websites, and only with netlify server config, as I tested setting differnt FTP on both sites and they do not override.

    #5824
    Tomasz Dziuda

    Hi,

    Thanks for the report – I will analyze this case and if I will be able to reproduce it – I will try to prepare a fix 🙂

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

    #6060
    Tomasz Dziuda

    Hi,

    The reason behind this issue is caused by fact that the UUID is not changed in password fields during cloning a website.

    In v.0.38.3 we will reset the deployment data during cloning: https://github.com/GetPublii/Publii/issues/1003

    But for previously cloned websites the easiest solution is to open site.config.json file and just remove password references under the deployment object e.g. “publii uuid-0319404494902-249420924” – it is an only way to easily remove the invalid binding between old and cloned websites.

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

    #6074
    NitaaiKumar

    There seems to be only one password reference in the site.config.json file. I closed Publii and tried removing them for both the original and duplicated site and then opening Publii and re-adding the server passwords for both of them but still only one site connects and the other one shows wrong password like before.

    So just to confirm that this fix will only work after you fix it in v.0.38.3 right? It won’t work now? Thanks.

    #6084
    Tomasz Dziuda

    Could you check if your both websites have the same or different UUID in the site.config.json?

    --
    Do you appreciate the support you've received today? If so, consider donating to the Publii team by clicking here; we'll be sure to use your donation to make Publii even better!

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.