A service exception occurred. (403)

English General
1

image
image1465×756 67.4 KB

Running 5.2.10.3568, I keep getting this error: “a service exception occurred” (403)

I have already tried the workaround I found in a related thread but it still does not work. I even tried restarting the NAS but no luck.

I have attempted to configure the storage location both for current and old logs but even trying to save the config brings me this error.

Any ideas?

2

best would be to open a ticket, what is the NAS model ?

3

Hello,

i think it is the same problem

I think too you open a ticket

5

If I am not mistaken, a TS-251. I will open a ticket tomorrow, at the earliest.

6

What makes you think the SMB problem you linked is the same at the QuLog issue I am seeing? Nowhere in my case was any mention of SMB: I am simply trying to access the logs and configure the settings.

7

I think it is a problem with the QTS-version 5.2.10.xx.
It is the first QTS-version with a 10.

8

Could you let us know whether you’re connecting via your local network or through remote access (such as VPN or myQNAPcloud)? Please also confirm whether this issue only started recently — for example, if everything was working fine before and it only became inaccessible now. Thanks!

9

I am connecting “locally”, meaning that… the browser is indeed in the same lan as the NAS but now I am going through a nginx reverse proxy for SSL (running in a container on the NAS itself, of course)

I haven’t checked QuLog in a looong time, but checking the logs there seems to be a gap. Now the unit is off, I can recheck this evening and update

10

oh ha… VERY interesting

  • plain http, direct: works fine even with QuLog
  • https via proxy: throws an error every time

I wonder why QuLog cares so much about it, since the rest of the UI seems to be fine

(but there is a gap in log archives between 19.06 and 06.07, which is when I tried clearing the config and restarting… so something still doesn’t quite add up)

11

Just run it plain via http then, if it’s locally in your network, there is no need for SSL or even a reverse proxy.

I remember discussions on the old forum where people complained that certain functions did not work if QTS web interface was going through a reverse proxy (sadly no way for me to check)

Here is some topic from reddit

https://www.reddit.com/r/qnap/comments/gdzkf5/comment/fwwsuai/?utm_source=share&utm_medium=web2x&context=3

12

thanks for the link, I’ll have a look!

13

There is no reason for going through a proxy server on your local network. You are behind your firewall and it’s all secure. Your NAS should not be published on the net. There’s no need to have hyper levels of security on the LAN.

14

I want https via letsencrypt because yes I do (learning, extra security, etc). The proxy was an attempt to do that. Attempt failed because no matter how many header rewrites I throw at it, the qnap backend / frontend js will still sniff out the proxy (especially for /nc/api) and throw 403.

myqnapcloud locks the domain name to qnap’s own choice even when using letsencrypt and introduces external access which I do not want, at all.

I will explore the possibility of replacing the builtin certificate: if that too fails, experiment failed and case closed :slight_smile:

EDIT: replacing /etc/config/stunnel/stunnel.pem with privkey+fullkey and restarting the daemon works, it survives reboots and I need to fix the automation without the proxy (another day)

15

Alright, I got acme.sh to work and it should survive both reboots and upgrades.

Where would I document it to help other users? I have noted all commands.

16

I would say put it here and maybe QNAP would make it an app note or something.

Glad you figured it out and good for you trying to learn all the security stuff!