@Adrian-Aguirre You may modify also the '/etc/opkg/customfeeds.conf' file and can use also OpenWrt 'snapshots' of course. Installing OpenWrt development snapshots In a nutshell: Q: I am a standard consumer, do I want a development snapshot firmware? A: No! In detail: Development builds / snapshots nano Version: 3.2-1 Dependencies: libc, libssp, libncurses So - I think - it's much more simple to use the usual method. Good luck.

@Zheng-Han said in omega2 uhttpd php7-cgi Bad gateway: @Mentor-Gashi try a factory restore firstboot and a clean install of onion-os and oos-app-editor it should configure php for you automatically make sure you are at the latest firmware build oupgrade -l Thanks, the -l flag did indeed upgrade the firmware despite the regular check was claiming the firmware was up to date. Going to give it a try if I can get a use of it

Finally found a solution: If you use your own custom webserver to setup the omega and want to display nearby Networks. <?php echo shell_exec("ubus call onion wifi-scan \"{'device':'ra0'}\""); ?> ^ This DOESN'T work! because: the php-interpreter doesn't have enaught ram to excute the command. It'll take a eternity. Solution: in /etc/php.ini set memory_limit form 8M to 32M memory_limit = 32M ; Maximum amount of memory a script may consume. now the scan only takes about 5sec.

@Yvan-Gagnon I've mentioned this a couple times in response to other posts and do not remember if one of those posts was yours, if so, I apologize for bringing it up again, but, it is possible to gain access to all the pins by using a female header with long pins. just insert the female header into each header of the mini dock and then insert [carefully] the omega2+ into the long pin female headers. this will leave all pins exposed that you can then use various methods to attach wires from your project to the appropriate pins. granted it is a "garage style" method and care must be taken to not damage the long pin headers, however it worked for any project i saw hooked up this way at a local hackerspace.

FYI even when I do /overlay and make a 2GB swap file, the version of node does crash on some instances like installing "azure-iot-device-amqp" the nodejs run time has its own buffer that needs to be increased, though from the error they posted I dont think its this issue. Another thing about npm installs is that in some cases you need python or some other dependency like git and npm builds the module on the onion, that takes a lot of resources. For my application I use 81% file storage and have 4.7mb left but I have these modules installed: azure-iot-common colors popsicle azure-iot-device file-queue raven azure-iot-device-amqp graceful-fs serialport better-queue node-json-db client-oauth2 omega2-io-pro If you want to do RESTful messages using Oauth2, I have successfully done so using "client-oauth2" and "popcicile"

I apologize for the misunderstanding. I wasn't really lamenting -- I was just explaining my current limitations and trying to figure out how to just leverage my current PHP configuration (which appears to also be pretty limited, I'm discovering) .. so I can somehow communicate with the Onion from outside of my local network. As it stands right now, it looks like I might need to have certain PHP extensions installed (such as the imap extension for php7) .. but that they might not exist for the particular Linux distro that's installed on the Omega. So far I've tried all of the following ... but none of them have worked. opkg install php-imap opkg install php7-imap opkg install php7.0-imap Am I missing anything here? Or am I correct in assuming that these packages simply don't exist for the Omega's Linux distro? Thanks, Yvan

I also have a similar problem, i was trying to get python' s psycopg2 to work on omega2+ but i cant seem to get pg_config for the omega installed, i also have opened a ticket ~1.5 months ago #7929 but still no reply/news from onion side

Have you checked version of MYSQL and PHPadmin. MYSQL 5.1.73-2 in the dist-feeds may only play nicely with PHPadmin 4.0.10.20

Ugh LITERALLY just figured it out For whatever reason, the document root is also specified in the /etc/php.ini file. (this is DUMB DUMB DUMB) See more here: https://community.onion.io/post/8605

@Joris-Mulliez I agree that PHP is of no use here, however I have plans to take this further, and wanted to start with the PHP base to work into. I am taking small steps into this whole new computing world for me. Yes, I could have just had the Python write out to "index.htm" and left it there, however what I am now doing is even beyond that. I want the initial page to allow for the selection of ZIP, City, PWS, Lat/Long and to set the refresh rate. This is only a backbone to grow from.

@Victor-Tagayun I don't know specific guides, this is more about experience with the services and reading man pages. Notice that you want to embrace a lot right now, you may desperate in some point. Hang on there. Remove console: The default web pages the Omega2 comes with are stored in some .../www directory, and the web server will have some info about the webpage to serve. All that may come in the docs, find them (you may encounter them while setting your own web) and then delete them, because if they are still up, someone from the internet could attack your Omega2 through the onion console. SSH no root login: ssh service must have a configuration file, for example in /etc/ssh.conf (I don't know if that is the file). Inside it, many parameters for the service, like the port to listen to, the possibility to login with name and password, if that login can be the user root, etc. The idea is that nobody can access as root from the internet, neither you, use serial to act as root. Also the web service shouldn't run as root, that's why you add another user, for example omega, with less privileges. Search google topic by topic, "ssh non root login", "linux add new user", "web service firewall recommended configuration", etc.

@Roman-Sierikov Just had the same problem but I see no reply. What worked for me is to add multiple entries: ... doc_root = "/www" doc_root = "/www/project1" doc_root = "/www/project2" ...