On Thu, Jul 06, 2017 at 07:40:35AM -0700, Galen Seitz wrote:
> Could someone else please try these two addresses and report if you see
> a similar problem? To the best of my knowledge, both of these are
> Newegg IPs.
>
> https://38.95.229.188
> https://216.52.208.188
Same deal using firefox, chr
On Thu, Jul 6, 2017 at 7:40 AM, Galen Seitz wrote:
> On 07/04/17 08:55, Galen Seitz wrote:
> > Hi,
> >
> > Yesterday I went to the newegg web site to buy a disk. I opened a
> > private browsing session in Firefox and went to newegg.com. I then
> > clicked on the login link on their home page.
It worked for me. I am using chrome. It will bark at anything that does not
even
smell right seems.
On Thu, Jul 6, 2017 at 10:10 AM, Galen Seitz wrote:
> On 07/06/17 07:49, Tim wrote:
> >
> >
> >> OK, tried it again this morning and got the insecure connection problem
> >> again. I also tried i
On Thu, 6 Jul 2017, Galen Seitz wrote:
> OK, that makes sense, and also explains why the SSL Labs test says I can't
> use IP addresses. Can you please try https://secure.newegg.com ? It's
> causing security errors here.
galen,
mozilla-firefox-45.9.0esr: connects correctly.
opera-45.0.2552.
On 07/06/17 07:49, Tim wrote:
>
>
>> OK, tried it again this morning and got the insecure connection problem
>> again. I also tried it with Chrome and got a similar security warning.
>> Could someone else please try these two addresses and report if you see
>> a similar problem? To the best of
> OK, tried it again this morning and got the insecure connection problem
> again. I also tried it with Chrome and got a similar security warning.
> Could someone else please try these two addresses and report if you see
> a similar problem? To the best of my knowledge, both of these are
> Newe
On 07/04/17 08:55, Galen Seitz wrote:
> Hi,
>
> Yesterday I went to the newegg web site to buy a disk. I opened a
> private browsing session in Firefox and went to newegg.com. I then
> clicked on the login link on their home page. At this point my memory
> gets a bit fuzzy, but I believe it was
On Thu, 6 Jul 2017, Jim Garrison wrote:
> Those are the IPs of the website, not the outgoing SMTP server. There's
> no reliable way to find out how a domain SENDS email. You can query DNS
> for the MX record to see where they RECEIVE email but not for the outgoing
> server. With an organization l
I'd like network admin help in trying to find where an expected e-mail
message gets lost before arriving here.
Each Tuesday evening an association's newsletter is distributed by the
marketing service Constant Contact (constantcontact.com) using the domain
name conta.cc. It does not arrive he
+1 for HandBrake - it is great for casual simple converting use - it
comes in two parts: CLI and GUI
If you ever need it, use ffmpeg for more complex tasks such as muxing
in/out different streams, and converting formats HandBrake does not
understand.
I would also recommend combination of x264 for v
10 matches
Mail list logo