Arctos: Media acting funny

[Jegelewicz]

I added media to a record this morning, both a video and a jpg. I attempted to upload thumbnails for both using the button on the manage media form and it didn't work.

I got the message about being haunted and not to use my back button.

I ended up loading the thumbnail as separate media, then adding that URI to the original media, which seemed to work (it saved), but when I view this media in the record, it appears like this

Instead of the thumbnail image, what is showing is the media description.

Media are as follows:

Video
JPG
thumbnail

Record they are associated with is NMMNH:Paleo:57623

[dustymc]

Investigating the button needs prioritized.

The rest is probably your browser caching or just being weird - that's the generated alt tag, I'm seeing thumbs.

[Jegelewicz]

I've cleared cache and this thing still looks this way

[Jegelewicz]

and the logo doesn't show on collection pages either.

[dustymc]

That's very likely in your network/environment.

[Jegelewicz]

OK, now it looks like this

And I haven't changed a thing in my network/environment.

[Jegelewicz]

And when I click on the right-hand bear, I expect to see the image, but instead I get this

[dustymc]

Are you somehow managing to load http://arctos.database.museum?

That looks like something isn't accepting https, or is trying to mix it with unencrypted, or similar, none of which should be easy to do.

[Jegelewicz]

I have no problem with anything else.

And now I am back to seeing this on the record

[Jegelewicz]

And when I go to edit the media, it looks like this

[Jegelewicz]

It just isn't consistent. Look at this one

[Jegelewicz]

With the same result when I try to view it

[dustymc]

That REALLY looks like something on your computer or in your network trying to mess with your encrypted traffic.

[Jegelewicz]

OK, I'll check with my network admin....

[Jegelewicz]

So, figured this out, but surprised others don't have issues.

For Firefox had to revert to tls version 1 and 2 (was 3) for website handshake.

Shouldn't TACC be using 3?

[dustymc]

Shouldn't TACC be using 3?

That's infrastructure - The Community and TACC (and perhaps the certificate issuer) need to come to an agreement.

I'm guessing this is coming from something that you, or someone who controls your machine or network, have installed. Identifying that could be useful.

[Jegelewicz]

It is a Firefox update! Which is why it is going to happen to everyone eventually.

[marecaguthrie]

I had the same experience and then after I updated firebox it started
working again but I didn't make the connection until reading this Teresa!
Good to know why it 'magically' fixed itself!

On Wed, Jul 22, 2020 at 9:34 AM Teresa Mayfield-Meyer <
[email protected]> wrote:

It is a Firefox update!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2889#issuecomment-662587548,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJKSRR7VA2XS37ABTGPCXDLR44PMFANCNFSM4OUUAO2A
.

--
Mareca Guthrie
Curator of Fine Arts & Associate Professor of Art
University of Alaska Museum of the North
1962 Yukon Drive
P.O. Box 756960
Fairbanks, AK 99775-6960
[email protected]

University of Alaska Museum of the North: www.uaf.edu/museum
UAF Art Department: https://www.uaf.edu/art/ https://www.uaf.edu/art/
Colors of Nature: http://www.colorsofnature.org/

[marecaguthrie]

I might have misunderstood your previous comment- but I was having similar
problems and now I am not...

On Wed, Jul 22, 2020 at 9:52 AM Mareca Guthrie [e-mail] wrote:

I had the same experience and then after I updated firebox it started
working again but I didn't make the connection until reading this Teresa!
Good to know why it 'magically' fixed itself!

On Wed, Jul 22, 2020 at 9:34 AM Teresa Mayfield-Meyer <
[email protected]> wrote:

It is a Firefox update!

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2889#issuecomment-662587548,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJKSRR7VA2XS37ABTGPCXDLR44PMFANCNFSM4OUUAO2A
.

--
Mareca Guthrie
Curator of Fine Arts & Associate Professor of Art
University of Alaska Museum of the North
1962 Yukon Drive
P.O. Box 756960
Fairbanks, AK 99775-6960
[email protected]

University of Alaska Museum of the North: www.uaf.edu/museum
UAF Art Department: https://www.uaf.edu/art/ https://www.uaf.edu/art/
Colors of Nature: http://www.colorsofnature.org/

--
Mareca Guthrie
Curator of Fine Arts & Associate Professor of Art
University of Alaska Museum of the North
1962 Yukon Drive
P.O. Box 756960
Fairbanks, AK 99775-6960
[email protected]

University of Alaska Museum of the North: www.uaf.edu/museum
UAF Art Department: https://www.uaf.edu/art/ https://www.uaf.edu/art/
Colors of Nature: http://www.colorsofnature.org/

[Jegelewicz]

HMMM, I was under the impression that the update caused the problem, but maybe it is the fix? We need a guinea pig....

[lin-fred]

I am having this issue on Chrome today. It was fine while I was physically at the museum at about 10am this morning, but now at 2pm today, I am on my home network and having this issue. I get the same problems as in Teresa's screenshots.

My Chrome is with update Version 84.0.4147.89 (Official Build) (64-bit)

[Jegelewicz]

This is the way you can fix it

https://github.com/ArctosDB/arctos/issues/2889#issuecomment-659072335

I didn;t write down the details and they are probably different for Chrome, but you can try Googling.

[AJLinn]

Version 84.0.4147.89 (Official Build) (64-bit)
Same problems in AK with Chrome (at home and at the museum on campus), works fine with Firefox.
I don't understand your comment re: fixing... something with encryptions or "website handshakes?"

[Jegelewicz]

[AJLinn]

Has anyone been able to successfully execute this on Chrome running on a mac? Google instructions are not showing me results I can use - they're all for PC.
Any guess as to why all of a sudden it's a problem?

[dustymc]

Has @ArctosDB/arctos-working-group-officers brought this up with TACC?

https://github.com/ArctosDB/arctos/issues/2889#issuecomment-662508398

Chrome doesn't complain for me so I'm not sure I can be much help with the specifics.

[AJLinn]

I'd recommend this be listed as Critical importance. For those of us who heavily rely on media to deliver content about our collections this is not acceptable.
@ArctosDB/arctos-working-group-officers, what do we need to do to fix this?

[lin-fred]

I'd recommend this be listed as Critical importance. For those of us who heavily rely on media to deliver content about our collections this is not acceptable.
@ArctosDB/arctos-working-group-officers, what do we need to do to fix this?

I agree, NMMNHS is about to "announce" our move to Arctos on main social media, updating our website, sending information up to the Governers office and requesting local news outlets to report on it.

I'll need to know if we should postpone. Our timing was going to be next week.

[Nicole-Ridgwell-NMMNHS]

I agree, NMMNHS is about to "announce" our move to Arctos on main social media

Agree, this is really critical for us at the moment. Our staff can get around with the disable TLS stuff, but that isn't going to work for the public.

[lin-fred]

Is there any update to this? @ArctosDB/arctos-working-group-officers

[AJLinn]

I haven't heard from any of the other AWG officers but I'll be sure to bring this up on Thursday for the AWG issues meeting. If you're able to attend we can add our voiced together to affirm the importance of managing it. I'm able to view okay in Firefox but Chrome is my primary browser and it continues to not show images. If we're having cross-program problems we can't expect our users to figure this out - it continues to be Priority Critical - @dustymc what do we need to say to TACC? Is it just telling Chris about the problem?

[dustymc]

Chris should just need to know that https://web.corral.tacc.utexas.edu is running TLS1.0 which causes some browsers to complain. (Which is a fairly ridiculous situation for us, but I suppose firefox can't know if your bank or an open-source JPG image is on the other end of the request....)

[AJLinn]

I'm able to view okay in Firefox

I stand corrected - now Firefox doesn't work.

[AJLinn]

@mkoo or @campmlc could you contact Chris about this as the heads of AWG? Is he a part of this Github account, that we could just tag him?

[lin-fred]

@Nicole-Ridgwell-NMMNHS I think we should wait on announcing Arctos

[Nicole-Ridgwell-NMMNHS]

@lin-fred agreed lets wait to set a date until this is resolved.

[Jegelewicz]

I emailed Chris Jordan today.

Chris,

We are having issues with viewing media stored at TACC (see Github Issue). I believe that the problem is that most browsers are auto-updating and set to use tls 3.0 while TACC is only responding to tls 1.0. While this can be solved for Arctos users by dialing back our browsers, it means that all public users will end up with errors when they attempt to view media stored at TACC.

Any way we can resolve this on your end?

Thanks!

Teresa J. Mayfield-Meyer

[AJLinn]

Thanks @Jegelewicz - I'm glad you had the right words to communicate our problem.

[Jegelewicz]

I have no idea if they are the right words - but the conversation has started!

[lin-fred]

Thank you!!!!

[campmlc]

I'm still having problems with this: cannot view

media associated with accessions and with catalog record:

[ewommack]

Me too! I just tried to access some MVZ egg images and got the same message.

[mkoo]

This is such a tricky issue that may be resolved with updates to clients (so my most disliked kind of issue)
We can discuss today but I cannot replicate these errors in FF and Chrome (probably because I allowed unsecure traffic on my fav websites)

Will follow up with Chris

[marecaguthrie]

Media images have disappeared for me in Firefox again (?!?)

On Thu, Aug 6, 2020 at 9:14 AM Michelle Koo [e-mail]
wrote:

This is such a tricky issue that may be resolved with updates to clients
(so my most disliked kind of issue)
We can discuss today but I cannot replicate these errors in FF and Chrome
(probably because I allowed unsecure traffic on my fav websites)

Will follow up with Chris

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2889#issuecomment-670062000,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJKSRR5VWA5OMCUNRQMZKMLR7LQI5ANCNFSM4OUUAO2A
.

--
Mareca Guthrie
Curator of Fine Arts & Associate Professor of Art
University of Alaska Museum of the North
1962 Yukon Drive
P.O. Box 756960
Fairbanks, AK 99775-6960
[email protected]

University of Alaska Museum of the North: www.uaf.edu/museum
UAF Art Department: https://www.uaf.edu/art/ https://www.uaf.edu/art/
Colors of Nature: http://www.colorsofnature.org/

[mkoo]

Update: this was discussed in various emails and in the Issues meeting today.
This requires updating TLS protocols on the media server at TACC, which will require updating the server OS and dependencies. Chris J. will plan this inperson operation for next week and hopefully without unforeseen issues will take care of all this browser behaviour! (for reference:
https://www.chromestatus.com/feature/5654791610957824)

Critical for @Nicole-Ridgwell-NMMNHS @lin-fred so they can make public announcements among other Arctos users.

[Nicole-Ridgwell-NMMNHS]

Thank you! That is great to hear.

[mkoo]

Sorry for forgetting to check with AWG at the meeting yesterday...
is this resolved now? (it was working for me so hard for me to test) @Nicole-Ridgwell-NMMNHS @campmlc @ewommack @AJLinn

[Nicole-Ridgwell-NMMNHS]

Nope, still getting

Have you heard anything from TACC?

[campmlc]

Yes, CJ just emailed and said he can do the upgrade to the media server
next Tuesday starting at noon Central. Arctos media will be down for a
couple of hours. I emailed BW about sending an announcement.

On Fri, Aug 14, 2020 at 12:30 PM Nicole-Ridgwell-NMMNHS <
[email protected]> wrote:

• [EXTERNAL]*

Nope, still getting
[image: image]
https://user-images.githubusercontent.com/47402809/90281449-d2ce9200-de29-11ea-84d6-85fad89d2cd2.png

Have you heard anything from TACC?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2889#issuecomment-674206816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ7JBBB5OBNSXLMPTGAN2TSAV7EXANCNFSM4OUUAO2A
.

[campmlc]

Modified from CJ email string:

The issue is with OpenSSL and other libraries behind Lighttpd, and I looked
into this when we did the switch to the Postgres environment and found it
not really feasible to update the whole stack on the present environment
(as in, you very quickly get to dozens of packages that would have to be
built by hand). The whole server OS will need to change.

In order to make the transfer I’ll need to take down the old web server and
transition DNS to the new one. This will, at minimum, result in some
disruption to the web access; I’m planning on doing this Tuesday afternoon,
so you may want to warn your community that media access will be down for a
couple of hours beginning Tuesday at 12 Central time.

On Fri, Aug 14, 2020 at 1:13 PM Mariel Campbell [e-mail]
wrote:

Yes, CJ just emailed and said he can do the upgrade to the media server
next Tuesday starting at noon Central. Arctos media will be down for a
couple of hours. I emailed BW about sending an announcement.

On Fri, Aug 14, 2020 at 12:30 PM Nicole-Ridgwell-NMMNHS <
[email protected]> wrote:

• [EXTERNAL]*

Nope, still getting
[image: image]
https://user-images.githubusercontent.com/47402809/90281449-d2ce9200-de29-11ea-84d6-85fad89d2cd2.png

Have you heard anything from TACC?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/2889#issuecomment-674206816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ7JBBB5OBNSXLMPTGAN2TSAV7EXANCNFSM4OUUAO2A
.

[Nicole-Ridgwell-NMMNHS]

Thank you for the update!

[Jegelewicz]

I believe this has been fixed. Closing