How do I setup Gmail priority labels with intricate filters?

I have a filter for important, unread and starred. Every time I try to change my Gmail priority inbox to the that label, it changes to: “All Everything Else.” It doesn’t matter if I try inbox #1, 2 or 3.

Here’s the label: “label:starred-important-and-unread” I made the filter by putting that string into the “Has words” section of the filter creation box.

Here are some screenshots

The filter

filter

The inbox:

inbox

What happens when I press save:

result

Please advise.

How to manually setup network connection from Busybox shell (ash)?

An embedded device running Linux version 2.6.26.5, ARM Linux Kernel. Busybox v1.10.2 shell (ash), I’m in Busybox shell. I want to set up connection between embedded device and computer. Is it possible manually set up network connection from Busybox shell? I mounted a main virtual file systems (proc, sysfs, tmpfs, /dev/pts), then entered commands to setup network, but without success. I guess, possibly, some modules or drivers were not loaded in this shell mode, but I’m not sure.

BusyBox v1.10.2 (2017-08-02 14:07:25 CST) built-in shell (ash) Enter 'help' for a list of built-in commands.  /bin/sh: can't access tty; job control turned off # mount -t proc proc /proc # mount -t sysfs sysfs /sys # mount -t tmpfs tmpfs /tmp # mount -t tmpfs tmpfs /dev # mkdir /dev/pts # mount -t devpts devpts /dev/pts # mdev -s # ifconfig lo 127.0.0.1 # ifconfig eth0 hw ether 88:75:56:05:6D:28 # ifconfig eth0 192.168.15.1 netmask 255.255.255.0 broadcast 192.168.15.255 # ifconfig eth0 up # route add -net 192.168.15.0/24 eth0 # ifconfig eth0 eth0      Link encap:Ethernet  HWaddr 88:75:56:05:6D:28             inet addr:192.168.15.1  Bcast:192.168.15.255  Mask:255.255.255.0           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:0 errors:0 dropped:0 overruns:0 frame:0           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000            RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)           Interrupt:22   # ping 192.168.15.100 PING 192.168.15.100 (192.168.15.100): 56 data bytes From 192.168.15.100 icmp_seq=0 timed out 

PiVPN setup issues

I’ve installed PiVPN per the instructions on their site. It’s a business connection (static IP) through a SmartHub (latest version). Per the instructions I’ve setup port forwarding in the routers firewall settings. I’ve also run PiVPN’s debug and can’t see any issues. However when connecting via OpenVPN (MacOS and iOS) I get the following error:

CONNECTION_TIMEOUT ERR

I assume this means the port forwarding isn’t working, however I’ve followed BT’s instructions and everything seems correct. I’ve also tried enabling the routers DMZ mode and tried port locking, but both had no impact.

Running the command

pivpn -d 

Creates the following log file:

::: ::: :: PiVPN Debug :: ::: ::: :: Latest Commit :: ::: ::: commit 4b4445b4667576f22a01af3dafbb4063218c964f Merge: bd6a1e1 b75b36f Author: james-lasersoft <37112079+james-lasersoft@users.noreply.github.com> Date: Wed Apr 10 22:23:03 2019 -0500

Merge pull request #716 from jamfrade/patch-1  Fix Easy-RSA install :::                  ::: ::  Recursive list of files in   :: ::  /etc/openvpn/easy-rsa/pki    :: :::                 ::: 

/etc/openvpn/easy-rsa/pki/: ca.crt crl.pem Default.txt ecparams extensions.temp index.txt index.txt.attr index.txt.attr.old index.txt.old issued OfficeVPN.ovpn openssl-easyrsa.cnf private renewed revoked safessl-easyrsa.cnf serial serial.old ta.key

/etc/openvpn/easy-rsa/pki/ecparams: prime256v1.pem

/etc/openvpn/easy-rsa/pki/issued: OfficeVPN.crt server_aLdaaHpdOCAmdyox.crt

/etc/openvpn/easy-rsa/pki/private: ca.key OfficeVPN.key server_aLdaaHpdOCAmdyox.key

/etc/openvpn/easy-rsa/pki/renewed: private_by_serial reqs_by_serial

/etc/openvpn/easy-rsa/pki/renewed/private_by_serial:

/etc/openvpn/easy-rsa/pki/renewed/reqs_by_serial:

/etc/openvpn/easy-rsa/pki/revoked: private_by_serial reqs_by_serial

/etc/openvpn/easy-rsa/pki/revoked/private_by_serial:

/etc/openvpn/easy-rsa/pki/revoked/reqs_by_serial: ::: ::: :: Output of /etc/pivpn/* :: ::: ::: :: START /etc/pivpn/DET_PLATFORM :: Raspbian :: END /etc/pivpn/DET_PLATFORM :: :: START /etc/pivpn/INSTALL_PORT :: 1194 :: END /etc/pivpn/INSTALL_PORT :: :: START /etc/pivpn/INSTALL_PROTO :: udp :: END /etc/pivpn/INSTALL_PROTO :: :: START /etc/pivpn/INSTALL_USER :: pi :: END /etc/pivpn/INSTALL_USER :: :: START /etc/pivpn/NO_UFW :: 1 :: END /etc/pivpn/NO_UFW :: :: START /etc/pivpn/pivpnINTERFACE :: wlan0 :: END /etc/pivpn/pivpnINTERFACE :: :: START /etc/pivpn/setupVars.conf :: pivpnUser=pi UNATTUPG=unattended-upgrades pivpnInterface=wlan0 IPv4dns=192.168.1.254 IPv4addr=192.168.1.69 IPv4gw=192.168.1.254 pivpnProto=udp PORT=1194 ENCRYPT=256 APPLY_TWO_POINT_FOUR=true DOWNLOAD_DH_PARAM=false PUBLICDNS= OVPNDNS1=8.8.8.8 OVPNDNS2=8.8.4.4 :: END /etc/pivpn/setupVars.conf :: :: START /etc/pivpn/TWO_POINT_FOUR :: :: END /etc/pivpn/TWO_POINT_FOUR :: ::: ::: :: /etc/openvpn/easy-rsa/pki/Default.txt :: ::: ::: client dev tun proto udp remote 81.133.250.129 1194 resolv-retry infinite nobind persist-key persist-tun remote-cert-tls server tls-version-min 1.2 verify-x509-name server_aLdaaHpdOCAmdyox name cipher AES-256-CBC auth SHA256 auth-nocache verb 3 ::: ::: :: Debug Output Complete :: ::: :::

To check if the ports are forwarding I’ve tried a range of port lookup sites like https://portchecker.co/check, however each reports port 1194 is closed. Not sure if this is reliable however as they also report port 80 is also closed.

Any advice to diagnose / fix issue would be greatly appreciated. The hardware is a Raspberry Pi 3, connecting via WiFi to the router.

how to setup ssh tunnel to named virtual host

I’m currently setting up server inside our lab at Uni that will be used for multiple purposes including a bibliography database and a CI Server (Jenkins). In order to maintain clean separation of concerns, I have a jailed virtual host for each function along with an assigned internal domain name. Inside the lab, the arrangement works fine.

However, in order to connect to our lab from home, we need to first VPN into the Uni and then SSH into our lab’s gateway machine. From the gateway we can access any internal machines we need to reach, and use SSH Tunnels as needed.

I’m wondering if it is possible to access virtual hosts through a single SSH tunnel? Like Server Name Indication (SNI)? Or would I need to setup a proxy server like Squid? I gather that both DNS as well as HTTP traffic would need to be routed correctly. Can this be done using just hosts file settings?

Any advice would be much appreciated. Thanks!

404 Response from NGINX when trying to setup mediawiki short urls

I have NGINX setup to serve content over localhost with HTTPS. Using the following location block, I can serve mediawiki just fine (it is in the /w folder)

location ~ /w/(.*)(\.php)?$   {   index index.php index.html;   try_files $  uri $  uri.php /w/index.php =404;   fastcgi_pass 127.0.0.1:9000;   include fastcgi_params;   fastcgi_param SCRIPT_FILENAME $  document_root$  fastcgi_script_name;   fastcgi_param SCRIPT_NAME $  fastcgi_script_name; } 

However, when I try to setup short urls (https://localhost/wiki/Some_Page for example) using this guide, I always get 404 file not found. I’m using PHP-FPM as the upstream, for reference. Here is the full configuration I’m using with NGINX to achieve short URLs

worker_processes 1;  events {   worker_connections 1024; }  http {   include mime.types;   default_type application/octet-stream;   sendfile on;   keepalive_timeout 65;   gzip on;    log_format compression '$  time_local - "$  uri" $  status "$  http_referer" $  request_filename';   access_log /Users/nicholas.chambers/log/nginx/access.log compression;   error_log /Users/nicholas.chambers/log/nginx/error.log;    server {     listen 80;     server_name localhost;     return 301 https://$  host$  request_uri;   }    server {     listen 443 ssl http2;     server_name localhost;      ssl_certificate /Users/nicholas.chambers/nginx/ssl/cert.pem;     ssl_certificate_key /Users/nicholas.chambers/nginx/ssl/private.key;     ssl_session_timeout 1d;     ssl_session_cache shared:SSL:50m;     ssl_session_tickets off;      ssl_protocols TLSv1.2;     ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256';     ssl_prefer_server_ciphers on;     ssl_trusted_certificate /Users/nicholas.chambers/ca/intermediate/certs/chain.pem;      root /Users/nicholas.chambers;      allow 127.0.0.0/8;     deny all;      location ~ /wordpress/(.*)(\.php)?$   {       index index.php index.html;       try_files $  uri $  uri.php /wordpress/$  1/index.php /wordpress/index.php =404;       fastcgi_pass 127.0.0.1:9000;       include fastcgi_params;       fastcgi_param SCRIPT_FILENAME $  document_root$  fastcgi_script_name;       fastcgi_param SCRIPT_NAME $  fastcgi_script_name;     }      location ~ ^/w/(index|load|api|thumb|opensearch_desc)\.php$   {       include fastcgi_params;       fastcgi_param SCRIPT_FILENAME $  document_root/w/$  fastcgi_script_name;       fastcgi_pass 127.0.0.1:9000; # or whatever port your PHP-FPM listens on     }      location /w/images {     }      location /w/images/deleted {       deny all;     }      location ~ ^/w/resources/(assets|lib|src) {       try_files $  uri 404;       add_header Cache-Control "public";       expires 7d;     }      location ~ ^/w/(skins|extensions)/.+\.(css|js|gif|jpg|jpeg|png|svg)$   {       try_files $  uri 404;       add_header Cache-Control "public";       expires 7d;     }      location = /favicon.ico {       alias /w/images/6/64/Favicon.ico;       add_header Cache-Control "public";       expires 7d;     }      location /wiki/ {       rewrite ^/wiki/(?<pagename>.*)$   /w/index.php;       include fastcgi_params;       fastcgi_param SCRIPT_FILENAME $  document_root/w/index.php;       fastcgi_param PATH_INFO $  pagename;       fastcgi_param QUERY_STRING $  query_string;       fastcgi_pass 127.0.0.1:9000;     }      location = /robots.txt {     }   } } 

I haven’t made any changes to my LocalSettings.php, except for adding the following data

$  wgScriptPath = "/w"; $  wgScriptExtension = ".php"; $  wgArticlePath = "/wiki/$  1"; $  wgUsePathInfo = true; 

Thanks in advance!

How to solve Magento 2.3 Setup Version Errors

When running the command n98-magerun2 sys:setup:compare-versions I’m receiving the following errors:

+-------------------------------------+---------+---------+---------+--------+ | Setup                               | Module  | DB      | Data    | Status | +-------------------------------------+---------+---------+---------+--------+ | Amasty_AdminActionsLog              | 1.0.0   | 1.0.0   | 1.0.0   | OK     | | Amasty_Base                         | 1.5.0   | 1.5.0   | 1.5.0   | OK     | | Amasty_Geoip                        | 1.3.2   | 1.3.2   | 1.3.2   | OK     | | Amazon_Core                         | 3.0.0   | 3.0.0   | 3.0.0   | OK     | | Amazon_Login                        | 3.0.0   | 3.0.0   | 3.0.0   | OK     | | Amazon_Payment                      | 3.0.0   | 3.0.0   | 3.0.0   | OK     | | Auctane_Api                         | 2.0.21  | 2.0.21  | 2.0.21  | OK     | | MSP_ReCaptcha                       | 1.5.0   | 1.5.0   | 1.5.0   | OK     | | MSP_TwoFactorAuth                   | 2.2.0   | 2.2.0   | 2.2.0   | OK     | | MagePal_GmailSmtpApp                | 1.5.1   | 1.5.1   | 1.5.1   | OK     | | Magefan_Blog                        | 2.8.9   | 2.8.9   | 2.8.9   | OK     | | Magefan_Community                   | 2.0.4   | 2.0.4   | 2.0.4   | OK     | | Magetrend_Email                     | 2.0.3   | 2.0.3   | 2.0.3   | OK     | | Vertex_Tax                          | 100.2.1 | 100.2.1 | 100.2.1 | OK     | | Magento_AdminNotification           |         | 2.0.0   | 2.0.0   | Error  | | Magento_AdvancedPricingImportExport |         | 2.0.0   | 2.0.0   | Error  | | Magento_AdvancedSearch              |         |         |         | Error  | | Magento_Amqp                        |         |         |         | Error  | | Magento_Analytics                   |         | 2.0.0   | 2.0.0   | Error  | | Magento_AsynchronousOperations      |         |         |         | Error  | | Magento_Authorization               |         | 2.0.0   | 2.0.0   | Error  | | Magento_Authorizenet                |         | 2.0.0   | 2.0.0   | Error  | | Magento_Backend                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Backup                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_Braintree                   |         | 2.0.1   | 2.0.1   | Error  | | Magento_Bundle                      |         | 2.0.4   | 2.0.4   | Error  | | Magento_BundleGraphQl               |         |         |         | Error  | | Magento_BundleImportExport          |         | 2.0.0   | 2.0.0   | Error  | | Magento_CacheInvalidate             |         | 2.0.0   | 2.0.0   | Error  | | Magento_Captcha                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Catalog                     |         | 2.2.6   | 2.2.6   | Error  | | Magento_CatalogAnalytics            |         | 2.0.0   | 2.0.0   | Error  | | Magento_CatalogGraphQl              |         |         |         | Error  | | Magento_CatalogImportExport         |         | 2.0.0   | 2.0.0   | Error  | | Magento_CatalogInventory            |         | 2.3.0   | 2.3.0   | Error  | | Magento_CatalogInventoryGraphQl     |         |         |         | Error  | | Magento_CatalogRule                 |         | 2.1.0   | 2.1.0   | Error  | | Magento_CatalogRuleConfigurable     |         | 2.0.0   | 2.0.0   | Error  | | Magento_CatalogSearch               |         | 2.0.0   | 2.0.0   | Error  | | Magento_CatalogUrlRewrite           |         | 2.0.0   | 2.0.0   | Error  | | Magento_CatalogUrlRewriteGraphQl    |         |         |         | Error  | | Magento_CatalogWidget               |         | 2.0.0   | 2.0.0   | Error  | | Magento_Checkout                    |         | 2.0.0   | 2.0.0   | Error  | | Magento_CheckoutAgreements          |         | 2.2.0   | 2.2.0   | Error  | | Magento_Cms                         |         | 2.0.2   | 2.0.2   | Error  | | Magento_CmsGraphQl                  |         |         |         | Error  | | Magento_CmsUrlRewrite               |         | 2.0.0   | 2.0.0   | Error  | | Magento_CmsUrlRewriteGraphQl        |         |         |         | Error  | | Magento_Config                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_ConfigurableImportExport    |         | 2.0.0   | 2.0.0   | Error  | | Magento_ConfigurableProduct         |         | 2.2.1   | 2.2.1   | Error  | | Magento_ConfigurableProductGraphQl  |         |         |         | Error  | | Magento_ConfigurableProductSales    |         | 2.2.0   | 2.2.0   | Error  | | Magento_Contact                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Cookie                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_Cron                        |         | 2.0.0   | 2.0.0   | Error  | | Magento_CurrencySymbol              |         | 2.0.1   | 2.0.1   | Error  | | Magento_Customer                    |         | 2.0.13  | 2.0.13  | Error  | | Magento_CustomerAnalytics           |         | 2.0.0   | 2.0.0   | Error  | | Magento_CustomerGraphQl             |         |         |         | Error  | | Magento_CustomerImportExport        |         | 2.0.0   | 2.0.0   | Error  | | Magento_Deploy                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_Developer                   |         | 2.0.0   | 2.0.0   | Error  | | Magento_Dhl                         |         | 2.0.0   | 2.0.0   | Error  | | Magento_Directory                   |         | 2.0.2   | 2.0.2   | Error  | | Magento_Downloadable                |         | 2.0.2   | 2.0.2   | Error  | | Magento_DownloadableGraphQl         |         |         |         | Error  | | Magento_DownloadableImportExport    |         | 2.0.0   | 2.0.0   | Error  | | Magento_Eav                         |         | 2.1.1   | 2.1.1   | Error  | | Magento_EavGraphQl                  |         |         |         | Error  | | Magento_Elasticsearch               |         |         |         | Error  | | Magento_Email                       |         | 2.0.0   | 2.0.0   | Error  | | Magento_EncryptionKey               |         | 2.0.0   | 2.0.0   | Error  | | Magento_Fedex                       |         | 2.0.0   | 2.0.0   | Error  | | Magento_GiftMessage                 |         | 2.0.1   | 2.0.1   | Error  | | Magento_GoogleAdwords               |         | 2.0.0   | 2.0.0   | Error  | | Magento_GoogleAnalytics             |         | 2.0.0   | 2.0.0   | Error  | | Magento_GoogleOptimizer             |         | 2.0.0   | 2.0.0   | Error  | | Magento_GraphQl                     |         |         |         | Error  | | Magento_GroupedImportExport         |         | 2.0.0   | 2.0.0   | Error  | | Magento_GroupedProduct              |         | 2.0.1   | 2.0.1   | Error  | | Magento_GroupedProductGraphQl       |         |         |         | Error  | | Magento_ImportExport                |         | 2.0.1   | 2.0.1   | Error  | | Magento_Indexer                     |         | 2.1.0   | 2.1.0   | Error  | | Magento_InstantPurchase             |         | 1.0.0   | 1.0.0   | Error  | | Magento_Integration                 |         | 2.2.1   | 2.2.1   | Error  | | Magento_LayeredNavigation           |         | 2.0.0   | 2.0.0   | Error  | | Magento_Marketplace                 |         | 1.0.0   | 1.0.0   | Error  | | Magento_MediaStorage                |         | 2.0.0   | 2.0.0   | Error  | | Magento_MessageQueue                |         |         |         | Error  | | Magento_Msrp                        |         | 2.1.3   | 2.1.3   | Error  | | Magento_Multishipping               |         | 2.0.0   | 2.0.0   | Error  | | Magento_MysqlMq                     |         |         |         | Error  | | Magento_NewRelicReporting           |         | 2.0.1   | 2.0.1   | Error  | | Magento_Newsletter                  |         | 2.0.1   | 2.0.1   | Error  | | Magento_OfflinePayments             |         | 2.0.0   | 2.0.0   | Error  | | Magento_OfflineShipping             |         | 2.0.1   | 2.0.1   | Error  | | Magento_PageCache                   |         | 2.0.0   | 2.0.0   | Error  | | Magento_Payment                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Paypal                      |         | 2.0.1   | 2.0.1   | Error  | | Magento_Persistent                  |         | 2.0.0   | 2.0.0   | Error  | | Magento_ProductAlert                |         | 2.0.0   | 2.0.0   | Error  | | Magento_ProductVideo                |         | 2.0.0.2 | 2.0.0.2 | Error  | | Magento_Quote                       |         | 2.0.8   | 2.0.8   | Error  | | Magento_QuoteAnalytics              |         | 2.0.0   | 2.0.0   | Error  | | Magento_QuoteGraphQl                |         |         |         | Error  | | Magento_ReleaseNotification         |         | 2.2.0   | 2.2.0   | Error  | | Magento_Reports                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_RequireJs                   |         | 2.0.0   | 2.0.0   | Error  | | Magento_Review                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_ReviewAnalytics             |         | 2.0.0   | 2.0.0   | Error  | | Magento_Robots                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_Rss                         |         | 2.0.0   | 2.0.0   | Error  | | Magento_Rule                        |         | 2.0.0   | 2.0.0   | Error  | | Magento_Sales                       |         | 2.0.10  | 2.0.10  | Error  | | Magento_SalesAnalytics              |         | 2.0.0   | 2.0.0   | Error  | | Magento_SalesInventory              |         | 1.0.0   | 1.0.0   | Error  | | Magento_SalesRule                   |         | 2.0.3   | 2.0.3   | Error  | | Magento_SalesSequence               |         | 2.0.0   | 2.0.0   | Error  | | Magento_SampleData                  |         | 2.0.0   | 2.0.0   | Error  | | Magento_Search                      |         | 2.0.4   | 2.0.4   | Error  | | Magento_Security                    |         | 2.0.1   | 2.0.1   | Error  | | Magento_SendFriend                  |         | 2.0.0   | 2.0.0   | Error  | | Magento_Shipping                    |         | 2.0.0   | 2.0.0   | Error  | | Magento_Signifyd                    |         | 2.2.0   | 2.2.0   | Error  | | Magento_Sitemap                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Store                       |         | 2.1.0   | 2.1.0   | Error  | | Magento_StoreGraphQl                |         |         |         | Error  | | Magento_Swagger                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_SwaggerWebapi               |         | 1.0.0   | 1.0.0   | Error  | | Magento_SwaggerWebapiAsync          |         |         |         | Error  | | Magento_Swatches                    |         | 2.0.3   | 2.0.3   | Error  | | Magento_SwatchesGraphQl             |         |         |         | Error  | | Magento_SwatchesLayeredNavigation   |         | 2.0.0   | 2.0.0   | Error  | | Magento_Tax                         |         | 2.0.3   | 2.0.3   | Error  | | Magento_TaxGraphQl                  |         |         |         | Error  | | Magento_TaxImportExport             |         | 2.0.0   | 2.0.0   | Error  | | Magento_Theme                       |         | 2.0.2   | 2.0.2   | Error  | | Magento_Tinymce3                    |         |         |         | Error  | | Magento_Translation                 |         | 2.0.0   | 2.0.0   | Error  | | Magento_Ui                          |         | 2.0.0   | 2.0.0   | Error  | | Magento_Ups                         |         | 2.0.0   | 2.0.0   | Error  | | Magento_UrlRewrite                  |         | 2.0.1   | 2.0.1   | Error  | | Magento_UrlRewriteGraphQl           |         |         |         | Error  | | Magento_User                        |         | 2.0.3   | 2.0.3   | Error  | | Magento_Usps                        |         | 2.0.1   | 2.0.1   | Error  | | Magento_Variable                    |         | 2.0.0   | 2.0.0   | Error  | | Magento_Vault                       |         | 2.0.3   | 2.0.3   | Error  | | Magento_Version                     |         | 2.0.0   | 2.0.0   | Error  | | Magento_Webapi                      |         | 2.0.0   | 2.0.0   | Error  | | Magento_WebapiAsync                 |         |         |         | Error  | | Magento_WebapiSecurity              |         | 2.0.0   | 2.0.0   | Error  | | Magento_Weee                        |         | 2.0.0   | 2.0.0   | Error  | | Magento_WeeeGraphQl                 |         |         |         | Error  | | Magento_Widget                      |         | 2.0.1   | 2.0.1   | Error  | | Magento_Wishlist                    |         | 2.0.1   | 2.0.1   | Error  | | Magento_WishlistAnalytics           |         | 2.0.0   | 2.0.0   | Error  | +-------------------------------------+---------+---------+---------+--------+    143 setup errors were found! 

I’ve tried running bin/magento setup:upgrade and clearing all cache. But nothing has worked up to this point. How to troubleshoot / solve these errors?

Hyper-V Replication setup fails, can’t resolve hostname [Windows 2016 datacenter edition]

Ok, here i have something nasty.

  • 3 Windows datacenter 2016 servers, running since early 2018
  • Replication has been up and running since early 2018
  • in january 2019 the private certificates for replication expired and we didn’t notice it
  • yesterday we renewed all certificates on the 3 machines
  • We have have done this before and there were no problems

The 3 machines are called

  1. HV2016-1 (192.168.140.90)
  2. HV2016-2 (192.168.140.92)
  3. HV2016-3 (192.168.140.91)

To prevent things from going bad (the replicated data on the backup server was at least 3 months old) we removed the replication configuration from the running VM’s and removed the replicated VM from the backup server. (HV2016-3 is running on older hardware and has the lowest amount of running VM’s. But it is sufficient for replications.)

But now… Replicating data from HV2016-1 works great and without problems to both HV2016-2 and HV2016-3. Replicating data from HV2016-3 works great and without problems to both HV2016-2 and HV2016-1. Replicating data from HV2016-2 works great and without problems to ONLY HV2016-3. Replicating data from HV2016-2 to HV2016-1 results in a flickering pop-up when we enter the hostname and press next for setting up replication information. We can’t get past this screen and it flickers for ever.

[hostnames] The names HV2016-1,2 and 3 are all on all servers specified in the hosts file. All hosts-files are identical on all 3 servers.

What we tried:

  • Reboot the servers
  • ping on IP address 192.168.140.90 from HV2016-2: ping good
  • ping on hostname HV2016-1 from HV2016-2: ping good
  • tracert HV2016-1: resolves good
  • ipconfig /flushdns
  • nbtstat -R
  • added other hostnames for the same IP address in the hosts file on HV2016-2, but every name that resolves to 192.168.140.90 results in the flickering pop-up

So i am stuck at this and can’t explain why this happens.

In Go, how do you setup a black box test package with a local dependency import?

I’m trying to setup blackbox testing of my go package. I’ve read this answer on blackbox testing in Go, using the package myfunc_test strategy, also discussed in these posts: Lesser-Known Features of Go Test and Structuring Tests in Go.

The problem with this approach, is how to import the local copy of the library under test?

This is the example from Structuring Tests in Go:

user.go:

package myapp type User struct {     id int     Name string } func (u *User) Save() error {     if u.id == 0 {         return u.create()     }     return u.update()  } func (u *User) create() error { ... } func (u *User) update() error { ... } 

user_test.go:

package myapp_test import (     "testing"     . "github.com/benbjohnson/myapp" ) func TestUser_Save(t *testing.T) {     u := &User{Name: "Susy Queue"}     ok(t, u.Save()) } 

Both files are in the same directory (this is the one case where you can have two packages in the same directory).

The problem here is that the testing will be done against the remote copy of the library under test (from github.com/benbjohnson/myapp in this example). How can I execute this blackbox test against my local copy of the library? This is necessary during development, and pre-merge Ci runs.

Would this setup provide adequate security?

In the following scenario, I’m looking to see if I can provide adequate security as is or if there would be any tangible benefit to re-architecting things (like changing it so that the service in question would be in a DMZ, or something like that). Assume that the data I’m trying to protect is highly sensitive and it would be a major headline if it got exposed.

  • On a server that has access to the internal network (because we also need to access a database or other internal services), there will be a gRPC service that listens on a specific TCP port.
  • I know in advance that I only want a client from a single known, trusted IP to connect in, so we’ll create a rule in the external firewall to allow incoming TCP connections from that single IP to the IP endpoint of the gRPC service.
  • For encryption and authentication, we’ll also be doing TLS 1.2 mutual authentication on the gRPC service.

As far as what I’ve been able to think of, this should be more than acceptable because the only way to be able to connect in on that port would be to either legitimately have that IP (and it’s a static IP where we trust the entity that the IP has been assigned to) or to spoof it, and a potential attacker would have to know that you would have to spoof that specific IP, which seems very unlikely without insider information (and even then, you’d only be able to send in packets trying to damage things and wouldn’t get responses back because they’d route to the real IP, right?). Assuming that a malicious actor were to gain control of that IP, they’d still have to have the appropriate certificate to get through the TLS piece, know the type of protocol that they’re trying to exploit, potentially need application-layer credentials, etc. I only see this as a likelihood if the actual client machine that I expect to connect in gets compromised; as far as I know, it has good physical/network security around it, so I think this should be very improbable.

Additionally, what about if I didn’t firewall it at all? Would the security level still be acceptably high since you’d have to either have a legitimate certificate signed by the same CA as the server’s certificate, or have an exploit up your sleeve in order to get past the TLS authentication? I’d firewall it either way since there really is just a single client I want connecting in, but I’m also curious about this.

Are there other issues that I’m not thinking about, or any other good reasons that should lead me to abandon this sort of setup as insecure? Thanks in advance.