[email protected] project in your NAS

[Danabw]

Yeah, been crazy here, the press is camped outside my front door, phone calls/texts coming in like wild.

Going to have to get my speech ready.

 

[akahan]

Welcome to OUR world.

 

[Danabw]

Still losing contact with foldathome container for some reason...it's running fine, I can see it in Synology docker app, and in portainer, but can't access it's page at either:

<NAS IP>:7396
<NAS IP>:32787

Anything I should try specifically to keep this working. It was fine yesterday for a while, then when I went to check it it would not come up, and same today.

 

[jphermans]

Strange, have it here running on 2 devices (nas) and no problem with it. Have used linuxserver/foldingathome docker to run. Is port 7396 a problem? I see that it is mapped to another port!

 

[Danabw]

Yeah, nothing I did, it defaulted to that for some reason, mapping 32787 to the container port.

Maybe I'll try changing that mapping and see what happens...

 

[Danabw]

I mapped 7396 to 7396, tried to access it at https://192.168.10.5:7396 and it still fails. (Also tried http just for the heck of it.)

No idea why it worked yesterday for a while (using the old port mapping to 32787) and won't work now. Nothing has changed on my router or NAS in the last 24 hours, except Portainer install, but it stopped working yestarday before I installed Portainer.

 

[akahan]

Are you sure the NAS is still at 192.168.10.5?

 

[Danabw]

Yeah, it's a fixed IP I set up when I first set the NAS up, always use fixed IPs w/my NAS, printers, pi, and a few other devices. I'm also logging into the NAS via its IP so that's a final confirmation.

Really odd. I'm going to assign the container to a different port at random and see what that does...

Mapping other ports didn't help, so letting this issue go.

 

[akahan]

Firewall on NAS? I’m running out of ideas.

 

[Danabw]

Thanks, not using any NAS firewall features, all of that is handled by my EdgeRouter.

It's just really odd that it worked for a while and then stopped. Probably a family curse... ;-) If not for the current situation stuck at home I would not have spent this much time on it. LOL...boredom makes you do crazy things.

 

[Shadow]

I mapped 7396 to 7396, tried to access it at https://192.168.10.5:7396 and it still fails. (Also tried http just for the heck of it.)

It should be HTTP. But maybe give this Docker it's own IP address in your LAN. I dunno, maybe that'll help?


Stats as of now: [email protected] stats report

(Yes, I also cheated yesterday with my old AMD gaming PC... xD)

 

[NASAdzy]

Hi All,

New to NASLyfe and I've joined the team!

Folding as Adam (w/passkey)

 

[Danabw]

It should be HTTP. But maybe give this Docker it's own IP address in your LAN. I dunno, maybe that'll help?

(Yes, I also cheated yesterday with my old AMD gaming PC... xD)

Thanks, @Shadow - I've tried http and https and neither work.

Your other suggestion sounds interesting - how would I create an an IP address on my router for the fold container?

Also - is there anything here in my settings that would cause issues like this?

 

[akahan]

Yes. Try unchecking the first one.

 

[Danabw]

Yes. Try unchecking the first one.

No joy after turning off the http to https redirect. And that was in place back when it worked a couple days ago so I'm still flummoxed about where/how I broke it. Thanks for hte suggestion. If @Shadow can tell me how to set an IP for a docker container I'll give that a shot.

 

[NASAdzy]

here's a snapshot of my docker logs.. note the new web connection line (when i log into the FAH local webpage.

Do you see that?

I had a bunch of problems using Brave web browser, but when i switch to FF.. the site loads up fine. wondering if maybe it's the client, not the container?

No joy after turning off the http to https redirect. And that was in place back when it worked a couple days ago so I'm still flummoxed about where/how I broke it. Thanks for hte suggestion. If @Shadow can tell me how to set an IP for a docker container I'll give that a shot.

 

[Danabw]

here's a snapshot of my docker logs.. note the new web connection line (when i log into the FAH local webpage.

Do you see that?

I had a bunch of problems using Brave web browser, but when i switch to FF.. the site loads up fine. wondering if maybe it's the client, not the container?

Excellent - thanks very much. Off to go logging...

I did try in Edge (primary browser is Chrome). Edge didn't work either.

 

[Danabw]

BINGO - Firefox works - I can pull up the page fine using the mapped port that Fold-at-home selects in auto mode. Thanks for reminding me to try FF, @NASAdzy. One of my usual troubleshooting steps when I have issues in Chrome, and totally forgot it.

I then cleared cache and cookie/data for the last 7 days in Chrome and the fold-at-home web control site then showed up in Chrome w/out issue. So something got twisted around in my cache/cookies on this, it looks like.

EDIT: Couple hours later and it won't load again. Still works in Firefox, and works in a Chrome incognito window, so that's how I'll view it for now.

 

[NASAdzy]

BINGO - Firefox works - I can pull up the page fine using the mapped port that Fold-at-home selects in auto mode. Thanks for reminding me to try FF, @NASAdzy. One of my usual troubleshooting steps when I have issues in Chrome, and totally forgot it.

I then cleared cache and cookie/data for the last 7 days in Chrome and the fold-at-home web control site then showed up in Chrome w/out issue. So something got twisted around in my cache/cookies on this, it looks like.

EDIT: Couple hours later and it won't load again. Still works in Firefox, and works in a Chrome incognito window, so that's how I'll view it for now.

View attachment 1272

I have the same experience in the Brave browser... !
I just use chrome or FF

 

[Shadow]

Your other suggestion sounds interesting - how would I create an an IP address on my router for the fold container?

No idea if it will make a difference, but check this post.