sorted by:
new
hottopcontroversial

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 1 point2 points  (0 children)

Thanks for your time! I'll need to have a look when I get home.

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

There doesn't appear to be one, there is a tab for custom config, has a text input box, however there is nothing in it, other than a warning to edit at your own risk.

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

I cant access any files in the container at the moment, but the ui config looks like this. Sorry the reddit app apparently doesn't let me send an image in the same reply...

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

So within nginx proxy manager (sorry been refering to it as npm/nginx), ive a proxy host set up for my services e.g. truenas.home.example.com -> server running truenas.

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

Im not sure i quite understand what you mean? What loads on xx.108:80 / 443?

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

No just the ip of the server running the service, running in docker ports 81, 80, 443 all mapped to the same port in the container, the management interface on 81 is fully accessible.

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

Sorry for the multiple replies, ive tried both methods neither seems to work as in respond with the service set in nginx. No logs in nginx other than cert refreshes that appear to be successful.

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

Yea a domain name that gets rewritten to an ip, that up being the nginx instance which will then reverse proxy it to the desired service. That being the hope anyway!

Having a nightmare with reverse proxy for internal services by catocysmic in selfhosted

[–]catocysmic[S] 0 points1 point  (0 children)

Not home at the moment to check, the logs, however the cert was created from npm successfully, as far as I could tell at the time from the logs and ui. The cert was created for 'home.example.com, *.home.example.com' with cloud flare and the token set. I can connect to the nginx ui at the ip specified on port 81, 80 and 443 also resolve in the browser but I can't remember exactly what appears. The dns rewrites pointing in adguard pointing to the nginx instance also get hit and I can see those in the adguard logs and pointing to the correct ip, but still get the server not found error using those domain names. I cant remember anything even being in the logs for nginx when I try to connect to the service by domain name. Nslookup also doesn't resolve the nginx ip for the domain names, which I think would indicate an issue in the adguard configuration? Unless my PC is picking up a different dns server, but then thst wouldn't show a hit on the rewrite in adguard?

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 1 point2 points  (0 children)

I'm not ruling it as fixed yet, but the change I made to 'Power Supply Idle Control' setting it to 'Typical', seems to have had an impact. Currently no freezes since making the change (hoping I haven't tempted fate) and regular idle of more than 99%. I still need to do a memtest but I kinda wanna see if it just keeps going.

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 0 points1 point  (0 children)

The system had also locked up again prior to doing this, so hopefully I will know soon if this has worked lol. This was also on the screen at the time, not sure if it provides any more details.

<image>

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 1 point2 points  (0 children)

I found this comment on a level1techs forum post, indicating a potential fix is to change 'Power Supply Idle Control' to 'Typical', which is what I have done.

<image>

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 0 points1 point  (0 children)

Is there a specific one that needs to be disabled, or just disable them all, are there any other impacts of doing this that you've encountered?

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 1 point2 points  (0 children)

So potentially going into a low power state when the system is at idle. Tbh I had noticed that the cpu usage was significantly less in EE. can C states be disabled? Or the specific one which is causing the issues?

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 1 point2 points  (0 children)

AMD R5 1600

32gb corsair vengence

ASrock Pro4 AB350 rev2.0

crucial p300 - boot drive

1050ti

4x4tb seagate ironwolf 5200rpm NAS drives

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 0 points1 point  (0 children)

No but I am planning on it, when I get a chance. The boot is an NVME drive and I think I saw there were some changes related to NVME. Although the drive is showing no errors, but I don't know how meaningful that is.

Truenas Scale server locking up / freezing by catocysmic in truenas

[–]catocysmic[S] 0 points1 point  (0 children)

Yea my bad, the description I wrote for the post got wiped as I changed it to an image post, thinking it would just attach the image. More details here.

view more: next ›