1
router & port problems / Re: nginx 413 Request Entity Too Large
« on: September 08, 2023, 07:24:26 PM »
and this post is hfs related as the server thats being accessed is hfs where im trying to get https for
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hi,
If you are running Nginx on the same PC that runs HFS (along with it, on the same OS), then instead of using:Code: [Select]proxy_pass http://192.168.0.100:80;
Use the following:Code: [Select]proxy_pass http://127.0.0.1:80;
Check if this solves your problem (and then please report back the results here).
If you check this when posting a new thread/post, instead of going back to the message index, you return to the topic (and see your new post).
Cheers,
Leo.-
To tell the truth, I'm not an Nginx expert, so it's hard to tell you what the exact problem is (and why it doesn't work for you). Rejetto has released a Nginx package HERE (to have HTTPS support). You can try his package, or you can 'extract' the correct setting from it. I haven't tested it, but perhaps using it you could solve your issue. Unfortunately I have no other solution in mind.
Hi,
If you are running Nginx on the same PC that runs HFS (along with it, on the same OS), then instead of using:Code: [Select]proxy_pass http://192.168.0.100:80;
Use the following:Code: [Select]proxy_pass http://127.0.0.1:80;
Check if this solves your problem (and then please report back the results here).
If you check this when posting a new thread/post, instead of going back to the message index, you return to the topic (and see your new post).
Cheers,
Leo.-
THIS is the standalone build.pfp = profile picture
the build includes node.js internally. I don't know a different way.
you want it to be compatible with win7, but this requires node.js version to be 13.
I'm using node 16.
It means someone should work on making HFS compatible with node 13.
Latest version is 19.
what is pfp? profile picture?
I should have guessed it from your username
exe is one of the available options
https://github.com/rejetto/hfs/releases/download/v0.41.0/hfs-windows.zip
"Just live with it" (until it's fixed, possibly never). Thanks for the report, anyway. You can edit the template and remove the protection check, but it's not recommended (since it requires you to have knowledge to not break the template).
Wait a minute... I hear Rejetto's footsteps approaching coming here, possibly to suggest you to try the brand-new HFS v3, which you already know: is 100x much better (and 10x more bloated too, but sadly I can't run it on my WinXP to test it). So, I better leave you now before he comes.
See you next time, bye...
Sorry, I was busy, and I couldn't answer...
It's easy, follow these steps:
1) Right-click on the folder you allow uploads, and choose 'Properties...'
2) Go to 'File masks' tab, and on 'Upload filter mask' write this:
*.*
(for allowing any type of file)
or
*.htm*
(for HTML files only)
(this only allows: .htm and .html files)
If you need to allow several types, you can separate using ;
For example (more examples):
*.htm*;*.jp*g;*.txt;*.rar
(this only allows: .htm, .html, .jpg, .jpeg, .txt and .rar files)
I guess this also answer this question (since it's the same question)
Cheers,
Leo.-
sorry, you can't.
It's not designed for this kind of task.
Sorry, I was busy, and I couldn't answer...
It's easy, follow these steps:
1) Right-click on the folder you allow uploads, and choose 'Properties...'
2) Go to 'File masks' tab, and on 'Upload filter mask' write this:
*.*
(for allowing any type of file)
or
*.htm*
(for HTML files only)
(this only allows: .htm and .html files)
If you need to allow several types, you can separate using ;
For example (more examples):
*.htm*;*.jp*g;*.txt;*.rar
(this only allows: .htm, .html, .jpg, .jpeg, .txt and .rar files)
I guess this also answer this question (since it's the same question)
Cheers,
Leo.-