DirectAdmin 1.658

Grid layout CSS code for "traditional" sub-theme is updated to work with DA 1.658. Please make sure to update CSS customization if they were used.

Evolution skin | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com
 
Hello.
Now (after DA upgrade to 1.658) all nodejs apps on cl. selector gives errors when stopping (or starting) the application:

Code: 
FileNotFoundError: [Errno 2] No such file or directory: '"/home/USERNAME/domains/DOMAIN/public_html"/.htaccess' Traceback (most recent call last):  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselector/cl_selector.py", line 245, in run    self.run_stop()  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselector/cl_selector.py", line 476, in run_stop    self._print_data(self._selector_lib.stop_app(self._opts['--app-root'],                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselector/selectorlib.py", line 947, in stop_app    self.selector_old_lib.stop(user, app_root, doc_root, self.apps_manager)  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselect/clselectctlnodejsuser.py", line 362, in stop    clpassenger.remove_passenger_lines_from_htaccess(htaccess_filename)  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselect/clpassenger.py", line 357, in remove_passenger_lines_from_htaccess    lines = file_readlines(htaccess_filename, errors='surrogateescape')            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  File "/opt/cloudlinux/venv/lib64/python3.11/site-packages/clselect/utils.py", line 213, in file_readlines    stream = open(path, errors=errors)             ^^^^^^^^^^^^^^^^^^^^^^^^^FileNotFoundError: [Errno 2] No such file or directory: '"/home/USERNAME/domains/DOMAIN/public_html"/.htaccess'

Is it because of the new "quoted document root paths"? And how to fix this?
 
@Access_Denied, yes. As a temporary workaround you can create custom templates that would not quote document root paths and call command da taskq --run 'action=rewrite&value=httpd' to re-create web-server configs. With time CL should fix this issue.
 
Hello, is this normal?
1704800738064.png
 
@MiloW, not this should not be happening. Please open a support ticket so we could investigate it further. All updates seems to happen exactly every one hour. Maybe you have a cron-job executing da build update_versions hourly? Calling da build update_versions or /usr/local/directadmin/custombuild/build update_versions creates a task to perform DA upgrade via taskq.
 
No, I didn't touch that at all... maybe it's just a message that there is a version there to upgrade?

BTW I have a strange thing here:
1704805781234.png


It looks like I have 1.6.5.8 and the available update is older than the one I have?
 
DA 1.658 is available in the current release channel, version 1.657 is available in the stable release channel.

It seems like you are now running DA from current, but in directadmin.conf stable release channel is configured. You can check configured release channel with CLI command da config-get update_channel or via GUI.

Combined with your previous screenshot of update messages it seems DA continuously trying to downgrade to the version available in the stable release channel. Please check if DA running as webserver and DA binary on the file system is the same version. DA binary version from CLI can be checked with command da version.
 
Which channel should I have? I thought stable was the right one.

What happens in such a situation - DA blocks the downgrade?

I can see I have now 1.658 so it went through to the latest one and you changed it to current - should I leave it like that? I guess so?

Thank you!
 
DA by itself does not block downgrades. You can jump between different release channels (and in effect between different DA versions). This should not be happening and I think the problem is specific to your server. If you would open a support ticket we could request access to the server and find the root cause. This forum thread is not the best place for interactive debugging :). If you want to try fixing the issue yourself I would start by trying to update DA manually and see if it succeeds:
  • Check current DA binary version with da version.
  • Perform update via CLI with da update.
  • Check DA binary version again da version, compare it against the version reported in GUI.
It is possible to update to specific release channel (without changing preferred channel in the directadmin.conf) by adding release channel name to the update command da update stable or da update current.
 
You know it seems to be quiet now, I am leaving current and there haven't been any messages since then.
Thanks.
 
I have 1.658 on my system and update available - also 1.658? Strange stuff : )
 
Also, @fln - any idea why I get a neverending "updating now" in the panel? Can I move around or what?
 
I think this relates to your previous problem with continuous update. Changing release channel to match what version you had at that time only masked the problem. So the same problem resurfaced when a new update became available. Please open support ticket regarding this issue.
 
"This is an automated message notifying you that DirectAdmin has been successfully updated.
v1.658 (cf601b4) to v1.658 (55d6205)"
but it didn't finish on its own, I just went to messages... the update was like "running all the time" - strange.
 
fln said:
@jamgames2, yes. This release does not migrate to the new NGINX config format.

This change just makes sure HTTP2 is always enabled. This allows us to get rid of the SPACE_HTTP2 token and ensure it is no longer possible to disable HTTP2. New format nginx templates (where HTTP2 support is controlled by a separate config option in new line) are expected in the next DA version.
Click to expand...
The listen directive should also change. The http2 should be on a separate line.
I made this change in cutom/nano nginx_server_secure_sub.conf
listen |IP|:|PORT_443| ssl;
http2 on;
This works for the IPv4 on all clients, but not for the IPv6 line. There the http2 is still at the end of the listen directive.
How to change this for IPv6 ?
 
@Hendrik
It same as me. but you can't do anything, because it inside custombuild binary.

Just wait next release or future around 2-3 update, because DA must ensure all server already updating to current nginx version.
 
We are not moving the http2 on; block to a separate line to stay compatible with nginx 1.24.0 (stable) release.

If we updated the templates right now servers using nginx 1.24.0 would fail to start with:

Code: 
nginx: [emerg] unknown directive "http2" in /etc/nginx/directadmin-ips.conf:31

However nginx 1.25.x (mainline) works with both modes http2 on the listen line and on a separate line. Keeping the old format allows DA to work with both stable and mainline nginx versions. The price for this compatibility is those annoying yet harmless warnings.

Of course most of the users are using nginx mainline (1.25.x) version already, because this version is selected by CustomBuild.

We will perform the switch (to new config format) immediately when one of the following events will happen:
  • Latest Nginx stable version gets support for http2 on; directive.
  • Latest Nginx mainline version removes support for the listen ... http2 ...; parameter.
List of nginx versions (stable version is not that old - released in 2023-04-11):

 
You must log in or register to reply here.
Back
Top