Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating js-controller 5.x on Slave over admin "TypeError: Network Error when attempting to fetch ressource" #1963

Closed
Feuer-sturm opened this issue Jun 23, 2023 · 10 comments · Fixed by ioBroker/ioBroker.js-controller#2345
Assignees

Comments

@Feuer-sturm
Copy link
Collaborator

Describe the bug
I have just successfully updated my master to 5.0.5 via the Admin GUI.
When I tried to update my slave via the Admin GUI in the next step, I got the following error message:

Start update over admin UI
grafik

Slave is successful updated
grafik

First feedback from @foxriver76 "currently admin polls the wrong ip."

Versions:
Master
Admin 6.5.9
js-controller 5.0.5

Slave
js-controller 5.0.4

Screenshots & Logfiles
Log Slave

2023-06-23 20:24:12.448 - info: host.ioBrokerNew Controller will upgrade itself to version 5.0.5
2023-06-23 20:24:15.367 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Stopping controller
2023-06-23 20:24:15.463 - info: host.ioBrokerNew received SIGTERM
2023-06-23 20:24:15.474 - info: host.ioBrokerNew stopInstance system.adapter.history.1 (force=false, process=false)
2023-06-23 20:24:15.476 - info: host.ioBrokerNew stopInstance system.adapter.sql.0 (force=false, process=false)
2023-06-23 20:24:15.478 - info: host.ioBrokerNew stopInstance system.adapter.discovery.0 (force=false, process=false)
2023-06-23 20:24:15.514 - info: host.ioBrokerNew terminated
2023-06-23 20:24:19.599 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
2023-06-23 20:24:19.618 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
2023-06-23 20:24:55.444 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE]
changed 18 packages in 33s
81 packages are looking for funding
run `npm fund` for details
2023-06-23 20:24:56.129 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:24:57.143 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:24:58.148 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:24:59.149 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:00.160 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:01.169 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:02.174 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:03.184 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:04.189 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:06.204 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:07.209 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:08.221 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:09.225 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:10.236 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:11.240 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:12.247 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:13.253 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:14.257 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:15.267 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:16.273 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:17.280 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:18.280 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:19.285 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:20.296 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:21.298 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:22.309 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:23.308 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-06-23 20:25:29.132 - info: host.ioBrokerNew [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
2023-06-23 20:25:31.159 - info: host.ioBrokerNew iobroker.js-controller version 5.0.5 js-controller starting
2023-06-23 20:25:31.170 - info: host.ioBrokerNew Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2023-06-23 20:25:31.173 - info: host.ioBrokerNew hostname: ioBrokerNew, node: v18.16.0
2023-06-23 20:25:31.175 - info: host.ioBrokerNew ip addresses: 192.168.178.78 fe80::d4a0:37ff:fe8e:f0c1
2023-06-23 20:25:31.750 - info: host.ioBrokerNew connected to Objects and States
2023-06-23 20:25:31.796 - info: host.ioBrokerNew added notifications configuration of host
2023-06-23 20:25:32.976 - info: host.ioBrokerNew 61 instances found
2023-06-23 20:25:33.019 - warn: host.ioBrokerNew does not start any instances on this host
@Feuer-sturm Feuer-sturm changed the title Updating js-controller on Slave over admin "TypeError: Network Error when attempting to fetch ressource" Updating js-controller 5.x on Slave over admin "TypeError: Network Error when attempting to fetch ressource" Jun 23, 2023
@foxriver76 foxriver76 self-assigned this Jul 7, 2023
@foxriver76
Copy link
Collaborator

foxriver76 commented Jul 9, 2023

According to 5dc9f88 it should work with 6.5.9 but this seems to be the used version in this ticket. Can you verify, that 6.5.9 or higher was used for sure?

@Feuer-sturm
Copy link
Collaborator Author

@foxriver76 According to the screenshot in the first post admin version was 6.5.9
I will retest this issue with current admin version v6.6.0 and the new js-controller 5.0.7

@foxriver76
Copy link
Collaborator

@Feuer-sturm Thanks a lot, let me know, however, probably it is still present unfortunately

@foxriver76
Copy link
Collaborator

When do so, please also check browser console for an error log like Cannot find ip address: ....

@Feuer-sturm
Copy link
Collaborator Author

Feuer-sturm commented Jul 10, 2023

@foxriver76

Admin 6.6.0
update from js-controller 5.0.6 to 5.0.7

  • Update ioBroker Master over Admin UI -> passed
  • Update ioBroker Slave over Admin (which is running on iobroker Master) -> failed

Screenshot
grafik

Log Browserconsole

Connected: true instrument.ts:132
Translate: time instrument.ts:132
Translate: timeOffset instrument.ts:132
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).
2
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Anfrage schlug fehl). Statuscode: (null).

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.
2
Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

Quellübergreifende (Cross-Origin) Anfrage blockiert: Die Gleiche-Quelle-Regel verbietet das Lesen der externen Ressource auf http://192.168.178.78:8081/. (Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt). Statuscode: 200.

@foxriver76
Copy link
Collaborator

foxriver76 commented Jul 11, 2023

ist 192.168.178.78 der Slave?

Und Admin nutzt https, korrekt?

@foxriver76
Copy link
Collaborator

@Feuer-sturm

ist 192.168.178.78 der Slave?

Und Admin nutzt https, korrekt?

@Feuer-sturm
Copy link
Collaborator Author

@foxriver76
ist 192.168.178.78 der Slave? -> korrekt
Und Admin nutzt https, korrekt? -> nein, Admin wird ohne https betrieben aber mit "Authentifizierung"

@foxriver76
Copy link
Collaborator

Danke, ich vermute es braucht leider nochmal eine Änderung im Controller.

@foxriver76
Copy link
Collaborator

will be fixed in controller v5.0.8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants