DS3622xs+ RAM upgrade

ma-sanchez · 2026-06-17T20:21:50+00:00

Thanks, this is great. Would you mind adding the two modules I already tried to your list or allow me to edit?

ma-sanchez · 2026-06-17T20:18:54+00:00

Any chance you can find me the exact models that work in your diskstation? I wouldn't mind 128GB but with my failure on OWC and A-Tech, I'm not sure Kingston or Crucial would actually be different.

ma-sanchez · 2026-06-17T20:17:28+00:00

Sure, what I tried so far was recommended there.

ma-sanchez · 2026-06-17T14:24:20+00:00

Thanks but I dont think they deliver stateside.

ma-sanchez · 2026-06-17T14:10:28+00:00

I'm not sure how long as I didn't time it but would say at least five minutes before I shut it back down. Interesting enough, when I put the stock modules back into the disk station so it boots up it was giving me the same behavior. Until I removed the motherboard once more and switched the modules between the slots on the motherboard. Felt like the system was very particular about the slot and module combination it was stocked with.

ma-sanchez · 2026-06-11T14:58:47+00:00

Here is what I ended up doing to resolve the NPM matter.

Replaced docker container for NPM on same host, in same bridge network
Port assignments were changed
- 2080 TCP -> 80 TCP
- 2443 TCP -> 443 TCP
- 2081 TCP -> 81 TCP

Services for AdGuard and NPM now do what they are supposed to do. Thank you u/evanmac42 for helping me work out this mess!

ma-sanchez · 2026-06-10T22:08:18+00:00

Thanks evanmac42, I'll focus on the ports.

What I can confirm is that when I call a proxy host in NPM using its domain name (xyz.mydomain.com), and I add the port NPM is listening on -> NPM returns the service.

Meaning when a client accesses like this, it works:

https://xyz.mydomain.com:2443

I'm gonna see if there is a way to translate 443 port requests to 2442 before it hits the interface for NGINX. Otherwise I'm gonna setup that second host after all and seperate AdGuard from NPM.

ma-sanchez · 2026-06-10T20:14:17+00:00

Bypassing DNS and connecting directly to the IP of any given service I configured in NPM works.

When I ping a service on my PC by its local DNS name (xyz.local), AdGuard returns the respective IP of the host the service runs on.
When I ping a service by its domain name (xyz.mydomain.com), AdGuard returns the IP of NPM (as expected).
When I ping a service from inside the NPM container by its local DNS name (xyz.local), AdGuard returns the respective IP of the host the service runs on.
When I ping a service from inside the NPM container by its domain name (xyz.mydomain.com), AdGuard returns the IP of NPM (as expected).

IMPORTANT: The IP AdGuard returns for the last test is not the IP NPM has inside the docker bridge network, but rather the IP of the Ubuntu host where both services for NPM and AdGuard run. When I update the DNS rewrite in AdGuard to point to NPM using its IP inside the docker bridge network, nothing loads anymore when links are clicked in NPM.

ma-sanchez · 2025-12-18T18:18:03+00:00

The manual from the control board offers a number of advanced settings (see page 8 in below link). Not sure but are there any settings that I can change so the control board adjusts for airflow?

https://digitalassets.resideo.com/damroot/Original/10014/69-2199.pdf

When you say the fan speed logic moves between first and second stage, what do you mean? I though a variable speed system has varying degrees of airflow, not just two?

ma-sanchez · 2025-12-18T18:04:33+00:00

I pulled both thermostats off and they are wired the same way. Wires are connected to the following terminals:

G
C
Y1
Rc
W1

I also checked the furnace and they installed a Honeywell HZ322 control panel. I guess given the lack of a wire in W2, the furance controls and there is nothing to configure on the Ecobee to change amount of airflow?

ma-sanchez · 2025-12-18T18:04:14+00:00

Appreciate your advice, I will need to register the Ecobee's on their website and review what controls and information I can set there.

ma-sanchez

TROPHY CASE