localhost (and site) unable to search #40
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some system information before anything…
OpenRC, Artix Linux, Nginx, and,
iwd
as the connection manager.I took some stuff from the 'real world' example from the Nginx page, Nginx throws no syntax errors, which is good. It works. Everything is good.
Basically, everything works except when it comes to accessing network-required pages, such as Search or the Instances browser. The Nginx configuration uses the port
2323
and the server4g.stelladenihil.i2p
. It being an eepsite has nothing to do, since if something manages the port set by i2p, it will just work.I'll record an example if asked so. Here's the log if it helps:
Er, the result of the error is the search page result being a blank page. Forgot to mention.
WRONG BUTTON FUCKKKK
It tells you what to do. It failed to call
apcu_inc
, which is part of the APCU module. Please make sure you installed all of the required modules.https://git.lolcat.ca/lolcat/4get/src/branch/master/docs/apache2.md
^the first thing it tells you to do here is to install the required modules. Now, some people have been dealing with some issues trying to install these packages on arch based systems, and often ended up using the docker container. But you seem to have found a way to install PHP, so you should be good I guess.
Let me know if this helps.
The PHP package for APCU isn't available in neither the AUR nor the Artix repositories. I'm going to look inside Arch's repositories, but I don't promise anything.
Apparently, it is in the
extra
repo. I installed it and:I'm pretty sure that is the same error. Could I know if
php-apcu
runs as a service? Because that might mean I need to make a boot entry for it.Restart nginx. Also yes, it's a daemon.
I did. I restarted the
php-fpm
daemon, also. Also tried anotherphp-apcu
variant in theextra
repository, didn't work also.I don't know brother, everyone who has tried getting this to work on arch has failed until they tried the docker container. Don't hate yourself too much if you can't get it to work.
I guess I'll close this then? I might re-open it if I find a fix. For now, I'll try to get it running via weird shit.
Ok wait, I forgot to ask something: Should I probably clone the repository (or make a markdown file for you to commit) to update the nginx documentation? Especially to add the Arch Linux notice to it; alongside with what's known.
fuck
Yeah that'd be good. :)
Uh, @lolcat, could I know where your files for
php-apcu
are located? It might be a location issue, I tried looking at the Debian packages subdomain but I couldn't find something about the file locations.EDIT: Nevermind, I found the file locations.
It might just be something with the package, or something with configuration. Could you showcase your
/etc/php/conf.d/apcu.ini
file?The closest match I have is this
The path that probably matters is
/etc/php/8.2/apache2/conf.d/20-apcu.ini
though, since it's the one that's actually being used when you use apache2Alright, for some reason my version contains it commented:
I removed it and restarted Nginx and…
Basically, the same:
I'm thinking of editing the file which calls it, (which seems to be about cookies) but I'm a bit “special,” and will probably mess it up.
Another also, I think
/usr/lib/php/modules/apcu.so
might be of importance? It seems like a binary. Sorta. Maybe. I'm also going to start<abbr>
the locations from the file list.APCU is needed for pagination to work. I store encrypted data inside apcu keys, and encrypt it. This is why when you paginate results, you get these random characters in your url bar. These random characters are actually the decryption key to the pagination data.
But yeah. I wouldn't go the compile PHP from source route, that is a huge pain in the ass. You need to figure out every module you need at compile time, so there's a lot of guesswork involved.
Could you link the thread you have made on Artix forums?
Oh, and one last thing. If you did manage to install php-apcu, can you edit your php.ini to contain the following directive?
Then, restart nginx & php-fpm
Tell me if that does anything for you.
Oh fuck. It works.
I didn't set my proxy settings right, so don't worry about it.
When it renders half of it that means it crashed somewhere, are you sure
It wasn't that. Maybe I should avoid guessing this time.
Let me show you the logs real quick…
Yes! That's the extension I use to encrypt the npt tokens for pagination.
You need this extension: https://github.com/jedisct1/libsodium-php
Is it available in the repos?
It seems to be in the AUR,
php80-sodium
(along those lines)So, basically, I can't. It requires
libsystemd
.The PECL extension manager isn't on the main repositories, and the AUR package might be from the same folk.
what the hell?
Ok, if you can't get this to work, I can try moving to using openSSL extension. Is there a way for you to set that up?
I suppose that it is also a package, yes?
It's an extension, I believe. Does your package provider really not bundle ANY extensions at all? Can you even decode JSON?
Can you run these tests for me?
I don't think I can:
If possible, I'll beat the other Artix issue in terms of comments.
you didn't get any errors. OpenSSL should work
Is
print()
really supposed not to print, though?You forgot the
;
even worse:
PHP Parse error: syntax error, unexpected identifier "Object" in php shell code on line 2
Just reset your shell. If you don't put a
;
last command will be appended to the current one.Okay, nevermind, it was the
!
. ContinueOkay so, I don't remember if I mentioned that I installed
world/php-sodium
, which does nothing for some reason??? I mean, it's probably for other use cases but still, the fuck???Can you make sure libsodium is loaded?
If not, load the required module in php.ini
It just gives a bunch of flags:
Related to sodium is:
--with-sodium=shared
Here's
php-config
's output:Are you sure? I think that the AUR package have all of them you can compile it following this:
Now it is not needed anymore though?
And this may be unrelated not sure.
Let me try that. If it doesn't work, I'll try doing a symlink with
elogind
to where everlibsystemd
is stored.Yeah.
I'll also see if I can find out how to actually post in the forums -- It might be a
You can post after xx/xx/xx AM
-thing but I'm not sure.@bread I built
Using that.
I have x86 packages if you want them.
As fair as I know you can post in the forum but you have to wait 1or 2? minutes between posts.
I made an account but it got terminated; it might've been the fact that I was using an alias, but it seems stupid, since the email never arrived.
And, feel free to pass me the package! It really is just the current best choice for me. The other would be to use Docker, but I'd rather not.
I built php83 for 4get but in the end I used docker I do not know to how do it without.
Do you need php80 instead?
You need to change the sed command to right file.
I extracted the source and it is in
php-8.0.30/sapi/fpm/config.m4
.The error shows that you tried 8.3.7 version.
Check that the path is correct if you get an error again.
Here there are the files.
php83 is better, yes. It's a patch for php8.
Ok, so basically:
You just have to place the files where they should be — And, I don't know if I mentioned, but the AUR package did try to build
php83
from scratch (for some reason the compilation process for a single PHP package requireslibsystemd
(and also to bulid the entire thing)). Unpractical, but works.Image proof because I forgot to:
Big thanks to everyone who helped me with this dogshit issue, especially Will for giving me someone to talk to. I'll see if I can make AT LEAST some notices to the AUR package maintainer(s) or a post in Artix's forums to tell them about packaging
php-libsodium
and not whateverphp-sodium
is. I'll as well modify the Nginx documentation markdown file, just because.I'd like to run this on Artix too.
Can you explain how do it?
Basically, uncompress
php83-sodium-8.3.7-1-x86_64.pkg.tar.zst
(from uncompressing your tarball, or downloading from somewhere else) and moveetc/php83/conf.d/20-sodium.ini
andusr/lib/php83/modules/sodium.so
to their respective place in/
, replacing ‘php83’ with just ‘php’....Alternatively, uncompress the tarball and modify the
.PKGINFO
to remove everything that isn't needed. Here's what it looks like without edits, if you're curious:Then, compress it again to a tarball and finally run
sudo pacman -U /path/to/file.pkg.tar.zst
.Your previous thread was clear with all the commands it's all the rest that I do not know to how do it.
Did you use this https://git.lolcat.ca/lolcat/4get/src/branch/master/docs/apache2.md?
@root
Consider looking at my fork, it has an updated Nginx guide:
https://git.lolcat.ca/bread/4get/src/branch/master/docs/nginx.md
Awesome, I'm happy you managed to figure it out. Is the nginx guide missing anything or are you ready to merge?
Nah, it's not really missing anything. I think those are all the fixes I wanted to apply.