Good news, I got it working. . . mostly. Found a setup guide that showed me what I was doing wrong.

Only have one small issue left.
I can't get Emby to work on SSL. I have a certificate setup, but, I get this error in my browser when going https. (http works fine.)

R_END_OF_FILE_ERROR

From searching the web, it is common for proxies to give this error, but I can't figure out what I need to change if haproxy to correct it.
Emby is using a letsenecrypt certificate, and is is running remote access through 443.

Any help would be appreciated.

you get a browser warning or you the blocked site loads?

Not getting a warning
i Get the blocked sites or blocked ads

Did you solve this?
I don't have the same issue, but found your posting while looking for a working setup for proxying MS Exchange.
Would be great if you could share your latest and greatest setup ;-)

@rami
knowing that I have already installed and configured squid guard/ssl

@Abdou-Ahmed said in Squid + https:

just add it in mikrotik

well, please specify this, please what kind of Mikrotik???
I'm pretty prepared in the "picture" - Mikrotik...
(all our CATV traffic is provided by Mikrotik devices)

@dealornodeal said in Can't login to skype after using squid proxy:

ofcourse it may be hardware mailfunction or just MS Windows added some crappy things into BIOS management system..

pfSense / FreeBSD, cannot change the BIOS this is the fact...

Under UEFI you can win, modification like EasyBCD...
https://neosmart.net/EasyBCD/

I was on summer break, hence the late reply. I guess I started with step 7.

Thanks for your reply! I will give it a try.

i have the same problem, but doesnt seem to what reza3sw said. though seen i found it to stop working, i have had a change in internet service provider, and having a dual wan, i edited 1 of those for the new service. i did have a config backup a couple mpnths old that in a test i uploaded that on the new pfsense version, and it works.

The proxy config snippet generated from the whitelist uses the acltype dstdom_regex

acl aclname dstdom_regex [-n] [-i] .foo.com ...
# regex matching server [fast]
#
# For dstdomain and dstdom_regex a reverse lookup is tried if a IP
# based URL is used and no match is found. The name "none" is used
# if the reverse lookup fails.

Even if it used dstdomain before, the asterisk character was invalid syntax and possibly ignored by the parser.

Short answer:
You have to adapt your whitelist or patch the code.

For adapting your whitelist:
The dot-Character has a special meaning in regex. If you want to include the '.' as in '.microsoft.com', you have to escape it: '.microsoft.com'
(and: squid knows the end of the domain name, you don't have to append the '.' in the end)

The correct migration would be:
*.microsoft.com. → .microsoft.com

Thanks for your help @PiBa everything is clear to me now!
Benoit

@moti4553 help @stephenw10 Dear we still present the problem, I already put DNS to IP 127.0.0.1, but the problem there is that I do not see my internal applications, please could you give me a light

@Simbad

Hi,

This is not a problem, in fact, they have been in this version for a long time.
AV filtering on the firewall doesn't really have a reason for existence, especially since it only applies to http

the daily.cld is updated and this is the essential momentum

http://database.clamav.net/main.cvd
http://database.clamav.net/daily.cvd
http://database.clamav.net/bytecode.cvd

https://www.freshports.org/www/squidclamav

ba5e4004-0758-414d-b052-89a06f592b7e-image.png