Static LAN IP with Multiple keyhost aliases

A rPi zero’s wifi adapter is pinned to a LAN IP address: 192.168.X.115 The rPI has multiple SD cards, so the keyhost can be changed when the SD card is swapped out.

The syntax of /home/user/.ssh/known_hosts is:

|1|ET5YHru9z0l45vmF1ChrPMCtcbq=|HSS8KxtYUCQibngCKlVJIx6Ub2x= ecdsa-sha2-nistp256 AAAAdHAyNTYAAAAIbmlzdHAyNTYAAABE2VjZHNhLXNoYTItbmlzBBMMHoT+878ksXDXPkJXFEyM/E7OKssfoD+n035qY71+JkGA0KYIxSUwiYiwJLwO1MzWuMTWlPIUaX5gDr23rrhI=

Serverfault indicates to append the output of keyscan and the IP address to known_hosts. The above syntax does not seem to include the IP host address (maybe it is hashed?)

How can I generate an additional entry to add the new SD card hostkey to my 16.04 known_hosts file?

sequelize self association error Aliased associations must have unique aliases [migrated]

I’m using sequelize 4.32 and I was trying to write a self-association in one of the tables, I’m not sure if there is something else that I need to do to solve this relation, my goal is to get all the records in my table and include all the records associated with each one this is the error that I’m getting in the console:

You have used the alias adjucent_stands in two separate associations. Aliased associations must have unique aliases

below you’ll find my model:

module.exports = (sequelize, DataTypes) => {   const stands = sequelize.define('stands', {     id: {       type: DataTypes.INTEGER,       unique: true,       allowNull: false,       primaryKey: true,       autoIncrement: true,     },     name: {       type: DataTypes.STRING,       field: 'name',       unique: {         args: true,         msg: 'Name already exists ',       },     },     location: {       type: DataTypes.JSON,       field: 'location',     },     remote: {       type: DataTypes.BOOLEAN,       field: 'remote',       defaultValue: false,     },     created_at: {       type: DataTypes.DATE(3),       defaultValue: sequelize.literal('CURRENT_TIMESTAMP(3)'),     },     updated_at: {       type: DataTypes.DATE(3),       defaultValue: sequelize.literal('CURRENT_TIMESTAMP(3)'),     },   }, { freezeTableName: true, timestamps: true, underscored: true });    stands.associate = (models) => {     stands.hasMany(stands, { as: 'adjucent_stands' });   };    return stands; }; 

Issues with my nginx config / aliases / errors

I have a VPS running CentOS 7, and I’m having some trouble with a few pieces of software that I’m trying to run. My miniflux instance is working, but all the other software I’m trying to setup with aliases is not working. I know the config is a mess as I’ve just copy and pasted from various install documentations.



directive “index” is not terminated by “;” in /etc/nginx/sites-enabled/mysite.conf:54

Not sure why as index.php is followed by a semicolon

mysite.tld/budget (firefly-iii):

FastCGI sent in stderr: “Access to the script ‘/var/www/mysite/firefly-iii/public/index.php/login’ has been denied (see security.limit_extensions)” while reading response header from upstream, client: myip, server: mysite.tld, request: “GET /budget/login HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php-fpm/php-fpm.sock:”, host: “www.mysite.tld”

Not sure how to get around this without disabling security.limit_extensions which seems to be a bad idea

mysite.tld/walla (Wallabag):

FastCGI sent in stderr: “Unable to open primary script: /var/www/mysite/app.php (No such file or directory)” while reading response header from upstream, client:, server:, request: “GET /walla HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php-fpm/php-fpm.sock:”, host: “www.mysite.tld”

For some reason it’s trying to find app.php in the wrong folder

mysite.tld/wiki (Bookstack):

directory index of “/var/www/” is forbidden, client: myip, server: mysite.tld, request: “GET /wiki/ HTTP/1.1”, host: “www.mysite.tld”

It’s trying to list the directory index here instead of the index.php file for some reason

Here is my nginx config (with a few identifying infos changed)

server {           root /var/www/mysite;          # Add index.php to the list if you are using PHP         index index.html index.htm index.nginx-debian.html index.php;          server_name mysite.tld www.mysite.tld;          location / {                 # First attempt to serve request as file, then                 # as directory, then fall back to displaying a 404.                 try_files $  uri $  uri/ =404;                 # proxy_pass http://localhost:8080;                 # proxy_http_version 1.1;                 # proxy_set_header Upgrade $  http_upgrade;                 # proxy_set_header Connection 'upgrade';                 # proxy_set_header Host $  host;                 # proxy_cache_bypass $  http_upgrade;         }      # pass the PHP scripts to FastCGI server listening on         #     location ~ \.php$   {                include fastcgi.conf;         #     #   # With php7.0-cgi alone:         #   fastcgi_pass;         #   # With php7.0-fpm:         fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;         }      # deny access to .htaccess files, if Apache's document root         # concurs with nginx's one         #     #location ~ /\.ht {         #   deny all;         #}  location /flux/ {     proxy_pass;     proxy_set_header Host $  host;     proxy_redirect off;     proxy_set_header X-Real-IP $  remote_addr;     proxy_set_header X-Forwarded-For $  proxy_add_x_forwarded_for;     proxy_set_header X-Forwarded-Proto $  scheme; }  location /wiki/ {    alias /var/www/mysite/BookStack/public;    try_files $  uri $  uri/ /index.php?$  query_string;     } location ^~ /firefly-iii/ {    deny all; }  location ^~ /budget {    alias /var/www/mysite/firefly-iii/public;    try_files $  uri $  uri/ @budget;      location ~* \.php(?:$  |/) {       include fastcgi.conf;       fastcgi_param SCRIPT_FILENAME $  request_filename;       fastcgi_param modHeadersAvailable true; #Avoid sending the security headers twice       fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;    } }  location @budget {    rewrite ^/budget/(.*)$   /budget/index.php/$  1 last; }      location ^~ /walla {         # try to serve file directly, fallback to app.php    alias /var/www/mysite/wallabag/web;          try_files $  uri /app.php$  is_args$  args;     }     location ~ ^/app\.php(/|$  ) {         fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock;         fastcgi_split_path_info ^(.+\.php)(/.*)$  ;         include fastcgi_params;         fastcgi_param  SCRIPT_FILENAME  $  realpath_root$  fastcgi_script_name;         fastcgi_param DOCUMENT_ROOT $  realpath_root;         # Prevents URIs that include the front controller. This will 404:         # http://domain.tld/app.php/some-path         # Remove the internal directive to allow URIs like this         internal;     }      listen 443 ssl; # managed by Certbot     ssl_certificate /etc/letsencrypt/live/mysite/fullchain.pem; # managed by Certbot     ssl_certificate_key /etc/letsencrypt/live/mysite/privkey.pem; # managed by Certbot     include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot     ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot   }  server {     if ($  host = www.mysite.tld) {         return 301 https://$  host$  request_uri;     } # managed by Certbot       if ($  host = mysite.tld) {         return 301 https://$  host$  request_uri;     } # managed by Certbot           listen 80;          server_name mysite.tld www.mysite.tld;     return 404; # managed by Certbot     }   

Requests, URL aliases and Controllers

How does Drupal determine the Controller from the Request object ? At which point does the url-alias of a node determines the controller? (I’m referring specifically to case where the route isn’t defined but is calculated by the url-alias).

I would like to listen to an event (‘onKernelRequest’ I suppose) and before Drupal determines the controller under certain conditions (‘Content-Type’ of node) to change the controller from NodeViewController to my own controller.

Thanks, Yaron

Visibility SQL aliases

I’m generating a lot of to-be reused SQL. A question on the visibility of aliases in SQL. If I create a query as followed:

SELECT name, age  FROM tablea a JOIN     (SELECT pid, age       FROM tablea a      JOIN tableb b ON = tage ON = 

Would this generate any issues? Any pitfalls? As far as I know I can to ‘tage’ in this case as it is a regular table in my outmost query. Do not have to consider any inference from having the same table alias inside the join statement and in the outer SQL statement.

As I’m looking for good practices, possible pitfalls. I was advised on Stackoverlfow to repost the question here.

Priority of aliases files for Drush

I have an installation with lando. On the project, we have a directory drush with an aliases file for the project. This file defines aliases with the root specific for the lando architecture.

In my home directory, I have an aliases file in my .drush directory with the same name which define the same aliases but with a root different, specific for my local computer, outside from lando.

Both aliases files are detect by drush but the problem, the aliases file from the project is always take in priority, inside or outside from lando. But outside lando, files are never find like the root isn’t correct.

The weird thing is my colleagues haven’t this problem and the root is aliases file is correctly choice when they are outside from lando. We’re thinking we have forget a configuration somewhere but we don’t see what.

Someone has an idea?

Thank you.

when is it necessary to create aliases in the SQL Configuration Manager?

I am having a problem with connectivity in one of my transactional replications and when checking the situation with the SQL Server configuration manager

I see there are aliases. I was wonder why they have been created…

What aliases are used for in the SQL Server Configuration Manager?

Does it have anything to do that in this particular case the machines (publisher and subscriber) are on different domains?


How to apply Postfix aliases before handing off to Dovecot via LMTP? [on hold]

I’ll try to be as brief as I can explaining this.

I have a CentOS 7 server configured with Postfix, mail_version = 2.10.1, and Dovecot, version 2.2.36 (1f10bfa63).

I recently configured dovecot to process Sieve filtering rules, with the following configuration change in dovecot.conf:

protocols = imap pop3 lmtp 

As well as in 10-master.conf:

service lmtp {   unix_listener /var/spool/postfix/private/dovecot-lmtp {     group = postfix     mode = 0600     user = postfix   }    client_limit = 0 } 

And in Postfix, the line

local_transport = lmtp:unix:private/dovecot-lmtp 

was added.

This all works as intended, but I’m getting constant notifications that emails for root are in the deferred queue, as Dovecot is rejecting them. root itself should never be the end recipient of an email. As well, various other “fake” (valid addresses w/o user accounts) accounts are present in /etc/aliases, but Dovecot is responding saying they don’t exist.

The problem seems to be that, with this configuration, Postfix is sending local mail messages (that is to say, all of them) to Dovecot’s LMTP socket before it does any alias translation. root emails getting stalled are a symptom, but the underlying problem seems to be that Postfix is giving the original recipient’s name to the LMTP RCPT TO, and causing issues.

What’s the appropriate way to apply the alias table before delivery elsewhere?

postfix aliases seems to not match aliases seen in web based postfix.admin

I am trying to figure out where to start hunting down odd issues I am seeing with aliases between postfix.admin and my postfix setup. I can find where most the flatfile alias files are… I am new to admining this stuff totally and I had a few questions:

If I change an alias flat file do I have to reload said file or will postfix pick it up? (it doesn’t seem too).

for instance: my /etc/postfix/ has this in it:

virtual_alias_maps =    hash:/usr/local/aliases/system.v,                         hash:/usr/local/aliases/lists.v,                         hash:/usr/local/aliases/users.v,                         hash:/usr/local/aliases/test.v,                         hash:/usr/local/aliases/misc.v, 

Inside misc.v has an entry I was searching and searching for in postfix admin in the webinterface, and couldnt find. user1, user2, user3, myself 

I added myself to the list, and then sent a test email to and didn’t seem to receive it?

That was one thing I noticed.

The other thing is in postfix.admin we have aliases ( does not show up with the users user1,user2, user3, myself)…that is fine they seem separate.

But on the postfixadmin -> virtual list -> aliases on the web I have another list:

which has a ton of users in it, they all get emails when someone sends it to but I do not (even though is definitely in the list.

I can even create another alias:  

and add through the web and that works, just the above with many users in it does not ever send to, I am not sure why that list wont let me receive email when someone sends to that list.

So trying to slowly learn this and figure out where the disconnect seems to be on how postfix is setup on the server, and how postfix.admin is talking to it (or in this case not). I am totally puzzled as to why I do not get an email when someone sends something to, which is an alias list of about 25 others, yet if someone sends something to  

I get the email just fine. is in both lists.