SBIE2203 Failed to communicate with Sandboxie Service: *MANPROXY

[ganego]

Hello,

first of all, thank you for continuing to develop Sandboxie.
I use Sandboxie Classic x64 on Windows 7. I recently updated to 5.48.0 and since then when I use a sandboxed PotPlayer to play a video I get the following errors. This was not the case in the past, although I do not know anymore what version I used before (I think it was 5.46.1 since I found it in my download log).
Programs are not allowed to access the internet, admin rights are dropped, network files are blocked.

SBIE2203 Failed to communicate with Sandboxie Service: *
SBIE2203 Failed to communicate with Sandboxie Service: *MA
SBIE2203 Failed to communicate with Sandboxie Service: *MANP
SBIE2203 Failed to communicate with Sandboxie Service: *MANP
SBIE2203 Failed to communicate with Sandboxie Service: *MANPR
SBIE2203 Failed to communicate with Sandboxie Service: *MANPRO
SBIE2203 Failed to communicate with Sandboxie Service:
SBIE2203 Failed to communicate with Sandboxie Service: *MANPROX
SBIE2203 Failed to communicate with Sandboxie Service: *
SBIE2203 Failed to communicate with Sandboxie Service: *
SBIE2203 Failed to communicate with Sandboxie Service: *MANPROXY
SBIE2203 Failed to communicate with Sandboxie Service: *M
SBIE2203 Failed to communicate with Sandboxie Service: *MA
SBIE2203 Failed to communicate with Sandboxie Service: *MA
SBIE2203 Failed to communicate with Sandboxie Service: *MAN
SBIE2203 Failed to communicate with Sandboxie Service: *MAN
SBIE2203 Failed to communicate with Sandboxie Service: *MANPRO
SBIE2203 Failed to communicate with Sandboxie Service:
SBIE2203 Failed to communicate with Sandboxie Service: *MANPROX

Any idea why this suddently shows up? Does this "MANPROXY" belong to Sandboxie or PotPlayer?
Was there something not catched before or is there just now an error connected to it?
PotPlayer seems to work fine regardless, so I could just hide the messages, but still I'd like to know why they suddenly appear.

Thank you

[DavidXanatos]

could you please test older versions and pinpoint which version introduced the error

[ganego]

tl;dr: started with 5.45.0.

I downgraded/overwrite my Sandboxie with 5.43.5 then installed every consecutive version and they worked fine, but v5.45.0.for.windows.7.exe did not start the driver and had errors. I then installed 5.45.1 and it had the MANPROXY errors. I then installed 5.45.0 over it (which worked) and also had MANPROXY errors although now they had encoding errors I guess, see log:

SBIE2203 Failed to communicate with Sandboxie Service: *MANPROXY⒔
SBIE2203 Failed to communicate with Sandboxie Service: *M⒔
SBIE2203 Failed to communicate with Sandboxie Service: *MA⒔
SBIE2203 Failed to communicate with Sandboxie Service: *MAN⒔
SBIE2203 Failed to communicate with Sandboxie Service: *MANP⒔

Errors in some later version with also encoding error.

SBIE2203 Failed to communicate with Sandboxie Service: *MAN┠
SBIE2203 Failed to communicate with Sandboxie Service: *MANP┠
SBIE2203 Failed to communicate with Sandboxie Service: *MANPR┠
SBIE2203 Failed to communicate with Sandboxie Service: *MANPRO┠
SBIE2203 Failed to communicate with Sandboxie Service: ┠

[ganego]

It has something to do with File Migration.
I now installed 5.49.0 Plus version over my Classic and with my default file migration setting (don't migrate larger than 5 KB) it gives MANPROXY error. When I set it to 1000 KB, there is no error.

EDIT1: This is with the new SandMan by the way:

• First of all, I get this notification for whatever reason despite the checkbox is unchecked.
• Second this might be the file (when I deny this, the next file is V01.log).

EDIT2:

• The first file V01.chk (always 8 KB) seems not to be the issue, because when I set the file migration to 10 KB, the file gets copied but the MANPROXY error persists.
• When I set the limit to 600 KB, the V01.log (always 512 KB) file gets copied and the error is gone.
• In addition, with the 600 KB limit I get two additional files in that folder WebCacheV01.tmp (512 KB) & WebCacheV01.dat (56 MB (yes MB)).

[DavidXanatos]

@ganego could you please test the last build and report back

[ganego]

Updated Sandboxie Plus installation. No new driver installed since there was none for that release.
File Migration Limit set ro 5 kB.
Opened my video player and ran some files.

My sandbox also blocks internet access to all programs.

[DavidXanatos]

This is very strange, i can not reproduce this log corruption
but i think you can get rid of it by
removing PromptForInternetAccess=y
from your config

the MANPROXY queue is available only when using the plus ui, the classical ui should filter that error and not show it, but as the MANPROXY string for whatever reason gets broken it fails to ignore it as it does not match.

[ganego]

removing PromptForInternetAccess=y from your config

Does not exist in sandboxie.ini

[Media_No_Internet]

Enabled=y
ConfigLevel=8
AutoRecover=y
BlockNetworkFiles=y
Template=SkipHook
Template=FileCopy
Template=qWave
Template=WindowsFontCache
Template=BlockPorts
Template=LingerPrograms
Template=Chrome_Phishing_DirectAccess
Template=AutoRecoverIgnore
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Favorites%
RecoverFolder=%Desktop%
BorderColor=#00ffff,off,6
BoxNameTitle=n
ForceProcess=<PotPlayer>
ForceProcess=vlc.exe
NotifyInternetAccessDenied=n
ProcessGroup=<PotPlayer>,desktophook.exe,deskto~1.exe,desktophook64.exe,deskto~2.exe,killpot64.exe,killpo~1.exe,potplayermini64.exe,potpla~1.exe
DropAdminRights=y
ClosedFilePath=InternetAccessDevices
CopyLimitKb=600
CopyLimitSilent=y
OpenFilePath=%AppData%\PotPlayerMini64\
BlockNetParam=y
FakeAdminRights=n
ClosePrintSpooler=y
OpenPrintSpooler=n
AllowSpoolerPrintToFile=n
OpenSmartCard=n
NeverDelete=n
AutoDelete=n
AllowRawDiskRead=n
NotifyDirectDiskAccess=n

I use the classic UI because it uses less RAM and because the new UI spams me with these messages to copy a file for whatever reason. Oh, and also: MANPROXY...

[DavidXanatos]

I can not reproduce the ma proxy issue, for some reason the communication with the plus UI fails than this error is displayed.
In the next build you will have the option to disable these file copy prompts, forcing the behavioure of the classical UI that is denying the copy operation right away.
setting will be PromptForFileMigration=n