QuObjects Connection Refused

Don't miss a thing. Post your questions and discussion about other uncategorized NAS features here.
Post Reply
bret.miller
New here
Posts: 2
Joined: Tue Jun 28, 2022 9:18 pm

QuObjects Connection Refused

Post by bret.miller »

I am trying to get QuObjects working for a backup application that uses S3 compatible protocol, but as a standalone server, all I'm getting when a connection is attempted is "connection refused", even when attempting to connect from a device on the same IP subject.

Since img isn't working for me, here's a screen shot of the config https://cloud.gci.org/files/quobjects-c ... -06-28.png.

This is a TS-453DU running 5.0.0.2055 with QuObject 2.4.1409.

Any attempt to connect to port 8443 as configured using https protocol gets a connection refused, even using the direct IP address from the same IP subnet. It's not even getting to the authentication.

Any ideas what would cause this? How would I go about debugging it? The debug log is rather useless for this...
dosborne
Experience counts
Posts: 1811
Joined: Tue May 29, 2018 3:02 am
Location: Ottawa, Ontario, Canada

Re: QuObjects Connection Refused

Post by dosborne »

Sorry, I know essentially nothing about this app, but took a quick read on installing it (https://www.qnap.com/en/how-to/tutorial ... t-tutorial ).

Have you tried with the default port just in case? Http vs https? Are you running the QNAP firewall or have any other app that may be blocking the access or port?

Definitely stick to troubleshooting from the local subnet first (IMO) as that removes many variables. After that is resolved, then look to make other changes!to suit your overall needs.
QNAP TS-563-16G 5x10TB Seagate Ironwolf HDD Raid-5 NIC: 2x1GB 1x10GbE
QNAP TS-231P-US 2x18TB Seagate Exos HDD Raid-1
[Deadbolt and General Ransomware Detection, Prevention, Recovery & MORE]
bret.miller
New here
Posts: 2
Joined: Tue Jun 28, 2022 9:18 pm

Re: QuObjects Connection Refused *SOLVED*

Post by bret.miller »

Thank you! Sometimes we just need extra eyes. I didn't think to see if the default port would work when 8443 didn't. I'm rather a fan of sticking a number in front of 443 when the protocol is HTTPS but in this case for some reason, 8443 is blocked even when specified. But 8110 works fine.
Post Reply

Return to “Miscellaneous”