#crowsnest KIAUH reverse proxy install issue

58 messages · Page 1 of 1 (latest)

cedar basin
#

I used KIAUH to install crowsnest.. at first it wasn't starting, was set to use the same port I have fluidd on, so changed that, it runs, but now it's only listening on localhost

I check docs, they say:

no_proxy

If this is set to true, it forces ustreamer to listen on all available network interfaces.

Useful if you want to use crowsnest in 'standalone' mode. Not recommended if you used MainsailOS or KIAUH to setup.

I thought previously/assumed now that nginx would be handling reverse proxy so that it's accessible at /webcam on the same port as mainsail?

Did I miss something in setting it up or something?

low adderBOT
#

Ahoi @cedar basin!
Welcome to the Mainsail support-forum!
There is a problem with the tags you selected for this post. Please fix them to fit your question.
For further information on tags please check the readme: https://discord.com/channels/758059413700345988/1320321898009071616

To change the tags of this post:

  1. Open the ... menu on the top right corner of this post.
  2. Find Edit tags
  3. Select the checkbox of the correct tags.

Usually you just need to select one tag!
If you still have no idea which one to choose, feel free to ask here.

Note: This is an automated message

Thanks for your cooperation!

#

Ahoi @cedar basin!
It looks like you did not provide all the necessary information we need to help you.
Please upload your logfiles and a detailed description of your problem.
For further information see: https://docs.mainsail.xyz/faq/getting-help/discord#provide-information
Note: We only accept .log and .txt files as log files.
This is an automated message

Discord | Mainsail

We are glad to help and chat with you on our Community Discord, but if you need help and want the best support possible you should, follow a few simple rules:

cedar basin
#

log files not applicable, stupid bot

woven helm
#

Send your logs....

cedar basin
#

logs don't apply!

woven helm
#

Send your logs...

#

Just do as I say

#

Just send them please

cedar basin
#

/etc/nginx/conf.d/upstreams.conf had the wrong ports.

What log would I give?

#

the NGINX log that didn't go to the right port?

#

the log for crowsnest that had zero errors ?

woven helm
#

I want your crowsnest.log

cedar basin
#

like fuck off

#

it had no errors

#

because it started on it's own port

#

with no conflicts

woven helm
#

Doesn't matter

cedar basin
#

at first, it had a conflict

#

anyway

#

like i said

#

the issue was upstreams.conf

#

and had nothing to do with crowsnest anyway

woven helm
cedar basin
#

Not trying to insult you,

#

and I get it, so many people come every day and logs defintiely help

woven helm
#

Then don't write stuff like "fuck off"

#

Ok, then send your config instead

cedar basin
#

but I'm not an idiot and logs didn't apply here

#

neither does config

#

like I said

#

the problem is SOLVED

woven helm
#

I don't get it, why even bothering do discuss it

#

Ok, then I ask it now

#

What is the port you are using in Crowsnest

#

Next time just send your log or config

cedar basin
#
  1. KIAUH was used to install.
  2. Fluidd was configured with it to use 8080.
  3. crowsnest was subsequently installed, using 8080 as default and NOT ASKING for a port like KIAUH did for fluidd.
  4. KIAUH didn't detect the conflict.
  5. NGINX was thus configured incorrectly.
#

None of that would've been troubleshootable from a crowsnest config or log.

woven helm
#

This still doesn't answer my question

#

I was asking for the port you are now using in the crowsnest.conf

cedar basin
#

I understand your position in order to save time in the vast majority of cases, but it didn't apply here.

#

It doesn't matter, it's whatever port I now chose and also matches in upstreams.

woven helm
#

Why should Crowsnest ask for ports during installation, if you can just change it at any time in your config?

cedar basin
#

it's not crowsnest

#

it's kiauh

#

if kiauh is using crowsnest installer, whatever

#

kiauh asked for a port when I did fluidd, because it knew of the conflict

woven helm
#

Ok, please stop sending anything now, I will explain you my think process

#

Kiauh installs Mainsail and Fluidd with a port, if you install both. One will be run on 80, as that's the default port.
With the first UI installation, you setup a reverse proxy in nginx. Those are bound to 8080-8083 with /webcam, /webcam2, ... /webcam4.
Those ports are predefined, either you use them or don't. If you don't use 8080-8083 in crowsnest.conf, you can ofc not use the previously setup reverse proxy. Crowsnest is not setting it up for you, it's all done only by KIAUH, and it's intended like that. There is no reason to ask the user for, which ports they want to run the webcam reverse proxy on.
If you don't use the reverse proxy, you have to set no_proxy: true.

#

Not recommended if you used MainsailOS or KIAUH to setup.
That is written there, as you don't need to do it with a normal installation

#

That means, with the default port of 8080 in crowsnest.conf and the reverse proxy setup of 8080-8083

#

Now please explain your setup again

#

Or explain me what the issue is. After reading it again, you maybe only wanted to know, if you can change that during setup? If so, no you cannot

#

The proxy is fixed for these ports, more advanced users know how they need to change it themselves, for not advanced users it's just a question that will confuse

#

Btw, if you would have wrote again, what the problem would have been, we would have been a lot faster, as I just didn't get, what you actually want

#

But that's on me 😅

cedar basin
#
  1. I already blocked you.
  2. I already solved the problem.
  3. You're wasting your time.
  4. I already explained that, due to my 30+ years of experience in development, that I get why you ask for logs initially, most users are idiots and it's often the easiest way to understand the situation. HOWEVER, when someone who understands this thorougly, explains that and also explains that the logs don't apply here, you should use some critical thinking instead of just demanding logs over and over.
  5. I fully understand the issue, I've been doing websites longer than Google, coding even longer, so to say that I understand HTTP and NGINX inside out and backwards is an understatement.
  6. I conceeded that the issue had nothing to do with crowsnest and thus mainsail and thus really, the conversation here should have been ended then, anyway.

But I could've given every log file, and you wouldn't have been able to figure out the issue.

I could've given the entire print_data/config folder, and you couldn't figure out the issue.

Perhaps you could've looking at the configs when I first started, and had seen that fluidd and crowsnest were on the same port, however, they no longer were as I had already solved that, obviously, but at the point he asked, no. The only file that would've been applicable was upstreams.conf and even the mention of it would've been enough to solve my problem.

When someone who thorougly understands why you ask "logs" says "logs don't apply" in this situation, perhaps use critical thinking instead of just being like LOGS LOGS LOGS LOGS I CAN'T THINK I CAN ONLY SAY LOGS.

A simple "nginx reverse proxy, config is in upstreams" would've solved my issue.

I should mention, that if KIAUH's goal is to be easy and intuitive, this wasn't, but that's not an issue for here.

Have a nice day. Hope you fix your panty knot, if you are truly the chief engineer, I'm uninstalling mainsail - thanks for your hardwork but your attitude is shit.

#

To be frank, I have zero expectations for anyones help, if they want to provide it, great, if not, great, but I wasn't expecting anything from you specifically.

Thanks for contributing to open source, truly hope you can adjust your attitude. I get it sucks supporting noobs, but, no one is asking you to do that either, especially for free, no one expects anything and when we do get open source software and good docs, that's awesome and more than enough.