Can't use local network proxy

[ghost]

The last version form MS Store can't use local HTTP proxy(from 127.0.0.1 or localhost), but before version can use that. I have test the localhost proxy server by telegram desktop version(from MS Store), every things show that proxy server works normal. Could you fix? It's is a really important feature in some where.

[maxkatz6]

Could you fix?

I think, you can.
Because I am almost sure, that problem is same as here: https://stackoverflow.com/questions/33259763/uwp-enable-local-network-loopback

[ghost]

Could you fix?

I think, you can.
Because I am almost sure, that problem is same as here: https://stackoverflow.com/questions/33259763/uwp-enable-local-network-loopback

Thank you. I will test that solution. But I remember before version can user local proxy without any more setting, so I want to sure may be Unigram have some way to use local proxy or all UWP applications can't do that and some mistakes in my memory. Thank you again.

[FrayxRulez]

No, it has never been possible to use local proxy without enabling the local loopback. Sure thing Unigram might inform the users about this, when they try to.

[thawisakprasreod]

@Tirraon

[RajCodeLabs]

any fix?

[FrayxRulez]

any fix?

Yes, check users suggestions

[william2ai]

So any enhancement?

[Weirdo1312]

i still have this issue

[makisukurisu]

Hi, @Weirdo1312, have you tried enabling local loop back?

If not – try the following command:

Get-AppxPackage | %{$_.PackageFamilyName} | where{$_ -match "unigram"} | %{CheckNetIsolation LoopbackExempt -a -n="$_"}

It was suggested long-long ago in one of the messages in Unigram Insiders

If the problem persists – get back to us.

[Weirdo1312]

Hi, @Weirdo1312, have you tried enabling local loop back?

If not – try the following command:

Get-AppxPackage | %{$_.PackageFamilyName} | where{$_ -match "unigram"} | %{CheckNetIsolation LoopbackExempt -a -n="$_"}

It was suggested long-long ago in one of the messages in Unigram Insiders

If the problem persists – get back to us.

no, enabling it fixed it, thanks