Unable to publish changes - DShop IPFS

[phyninja]

I would like to know if you can help me with this problem .. I can't publish the changes to make the shop publicly visible, it always show me this message.

Originally posted by @GhassenMedyouni in #1005 (comment)

[GhassenMedyouni]

@phyninja I create my marketplace Dshop, I can't make it public, this is my Network config

the public URL still inaccessible

[kellyalb]

Hi,

could you try creating a free Piñata account and connect it via key/secret?

[phyninja]

@GhassenMedyouni, I stand by @kellyalb's response.

[GhassenMedyouni]

@kellyalb I create a Pinata account , but still the same issue

after i click publish nothing has been chnaging

[kellyalb]

Hmmm… in your first screenshot, is the box for “Piñata pinning” checked down below?

what happens if you try to deploy from the Super Admin > Shops > [your shop] > Deploy section?

also, I’ve had to stick with Infuria for gateway/api to keep things working

[GhassenMedyouni]

@kellyalb the deployment was worked, but i can't activate it.

[kellyalb]

That seems like progress. Activate doesn’t work for me either. I’m guessing now it may be up to how you are configuring your DNS. Do you feel confident in that part?

[GhassenMedyouni]

@kellyalb i think the problem is that there is no a DNS provider but how to add it. ??

[phyninja]

Hello,
To gain insight into why the 'Activate' button doesn't work, I looked into the source code for DShop. Like myself, you may also find the following error message displayed on your web browser's console when you click on the button:
Error setting hostname: 400: Bad Request

The error arises because the app expects a value in the DNS Provider field here:

@kellyalb would you please continue providing support?

[kellyalb]

I wasn’t able to get the DNS Provider functionality working in Dshop. I had to get Dshop working by manually configuring my DNS settings for my domain starting at its registrar. I’d need to double check the exact configuration that worked for me, but I believe it was a combination of A records and wild card sub domains.

@GhassenMedyouni do you have your Root Domain pointing to the IP address of the server where Dshop is installed? Then do you also point to the same IP address for all subdomains, by using a * for a wildcard, for that Root domain?

[GhassenMedyouni]

@kellyalb i create a new record with the public URL and point to the same address IP.

i want to have the access to the shop like a simple user

[GhassenMedyouni]

@kellyalb Hi again, I am stuck in the same step, the DNS provider always displays none, so I cannot activate the shop even though I have created new records for the subdomain with the same IP address. Thank you for your help until now.

[phyninja]

What is the result of using the route below?

1. Go to Settings > General from the DShop Admin console
2. Click on the Add a custom domain button and enter details
   
3. Update DNS records on the Domain registrar's side as directed

[GhassenMedyouni]

@phyninja I added a custom domain also i created a new record with the custom domain and i pointed to the same IP address.

after a few minutes

[phyninja]

@GhassenMedyouni

On Origin's Discord Server, there are some messages posted by users who also had trouble configuring DNS settings for DShop. I looked through those, but can't say that I found something that might help.

They say, however, that "DNS propagation may take up to 48 hours (to propagate)". Given that it has been over 48 hours since you posted, could you please check back in?

[phyninja]

@GhassenMedyouni, you said previously that "the DNS provider always displays none, so (you) cannot activate the shop even though (you) have created new records for the subdomain with the same IP address."

Since Kelly mentioned the workaround of configuring DNS settings from the Domain registrar's side, we should continue pursuing that route to fix this issue. What is the name of the Domain registrar you're using?

[GhassenMedyouni]

@phyninja, The domain name that I'm using is turnip.ovh hosted in route 53 Amazon.

[phyninja]

turnip.ovh

We need to take a moment to check the spelling. Can you confirm that it's turnip, not tunip?

[GhassenMedyouni]

turnip.ovh

We need to take a moment to check the spelling. Can you confirm that it's turnip, not tunip?

@phyninja sorry it's tunip

[phyninja]

Over a screen sharing session, @GhassenMedyouni and I worked together to:

• Launch a new EC2 instance from the DShop AMI
• Add 'Custom Domain' records on the Route 53 interface, and
• Configure the DShop Deployer.

I then

• created a new shop
• added a custom domain from Settings > General
• made (recommended) changes on the domain-registrar end, and
• attempted to publish the store.

The URL shown in the Host filed of the CNAME record directs a user to the DShop Admin console. The URL that the public can access the shop is to be determined.

[phyninja]

@GhassenMedyouni,

I found the place in our codebase that displays the error "Something went wrong. Try again later" (Ref: #1014 (comment)), but not the answer to the question of how the public can access your shop.

Could you help me by taking the following steps, and posting the result?

1. Start the DShop Instance
2. Go to the DShop Admin console > Settings > General
3. Copy the URL under 'Domain Name'
4. Open a new Private window in your web browser OR open a window in a different web browser
5. Navigate to the URL.

[phyninja]

We found that adding the following two DNS records allowed for @GhassenMedyouni's shop to 'go live' on a public URL:

Record Type	Record name	Host/Value
A	Backend Public URL	IP address of the EC2 instance
A	*.tunip.ovh	IP address of the EC2 instance

Credits:
#1014 (comment)
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/DomainNameFormat.html#domain-name-format-asterisk