Distributor's Certificate

I found an error today - it is impossible to create a distributor’s certificate in the Certificate Manager. Error: “Please check your proxy setting. Your connection is behind the proxy server”. The error is the same from different computers and networks. Internet said it was possible because of a broken resource: devicetest.samsungcloudsolution.com . Does anyone have any thoughts, or is it temporary error for Samsung?

3 Likes

The same issue. I can’t finish creating a certificate because of “Your connection is behind the proxy server“, although I’m not using any proxy…

1 Like

I also noticed a similar issue which I posted in another thread - Https://dev.tizen.samsung.com/ not reachable

Could be related.

1 Like

Me too, please somebody help us

1 Like

same problem, please help somebody

1 Like

Im having the same issue. Looks like dev.tizen.samsung.com is unreachable

$ wget https://dev.tizen.samsung.com/
--2025-09-12 13:14:24--  https://dev.tizen.samsung.com/
Resolving dev.tizen.samsung.com (dev.tizen.samsung.com)... 112.106.187.16
Connecting to dev.tizen.samsung.com (dev.tizen.samsung.com)|112.106.187.16|:443... failed: Connection refused.
2 Likes

I have same issue for a half days. They never have tried to figure it out.

1 Like

me as well. want to get how to fix it.

1 Like

Same Problem. Wait for help

Same here, guess we are all in the same boat.

Waiting for a fix

Same here :frowning:

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* Host dev.tizen.samsung.com:443 was resolved.

  • IPv6: (none)
  • IPv4: 112.106.187.16
    0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0* Trying 112.106.187.16:443…
    0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0* connect to 112.106.187.16 port 443 from 0.0.0.0 port 52181 failed: Connection refused
  • Failed to connect to dev.tizen.samsung.com port 443 after 3705 ms: Could not connect to server
    0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0
  • closing connection #0
    curl: (7) Failed to connect to dev.tizen.samsung.com port 443 after 3705 ms: Could not connect to server

Hopefully someone will provide a fix for this issue

No proxy, no VPN, but the same problem.

Same issue here!


I also created a support ticket